From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.comp.tex.context/110359 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Rik Kabel Newsgroups: gmane.comp.tex.context Subject: Using \overloaded Date: Sat, 23 Jan 2021 23:13:03 -0500 Message-ID: <5d5d6bb9-9598-3a49-409d-adf1d78e370f@rik.users.panix.com> Reply-To: mailing list for ConTeXt users Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============2745813434971211576==" Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="9590"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Firefox/78.0 Thunderbird/78.6.1 To: mailing list for ConTeXt users Original-X-From: ntg-context-bounces@ntg.nl Sun Jan 24 05:29:18 2021 Return-path: Envelope-to: gctc-ntg-context-518@m.gmane-mx.org Original-Received: from zapf.boekplan.nl ([5.39.185.232] helo=zapf.ntg.nl) by ciao.gmane.io with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1l3X1Z-0002Px-SK for gctc-ntg-context-518@m.gmane-mx.org; Sun, 24 Jan 2021 05:29:17 +0100 Original-Received: from localhost (localhost [127.0.0.1]) by zapf.ntg.nl (Postfix) with ESMTP id 6778F1C1B71; Sun, 24 Jan 2021 05:28:49 +0100 (CET) X-Virus-Scanned: Debian amavisd-new at zapf.boekplan.nl Original-Received: from zapf.ntg.nl ([127.0.0.1]) by localhost (zapf.ntg.nl [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id V605kTy0swQe; Sun, 24 Jan 2021 05:28:48 +0100 (CET) Original-Received: from zapf.ntg.nl (localhost [127.0.0.1]) by zapf.ntg.nl (Postfix) with ESMTP id 820C41C1C6F; Sun, 24 Jan 2021 05:28:48 +0100 (CET) Original-Received: from localhost (localhost [127.0.0.1]) by zapf.ntg.nl (Postfix) with ESMTP id 36C411C1B22 for ; Sun, 24 Jan 2021 05:28:47 +0100 (CET) X-Virus-Scanned: Debian amavisd-new at zapf.boekplan.nl Original-Received: from zapf.ntg.nl ([127.0.0.1]) by localhost (zapf.ntg.nl [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Mbc26jCeAr0z for ; Sun, 24 Jan 2021 05:28:46 +0100 (CET) Received-SPF: Pass (mailfrom) identity=mailfrom; client-ip=166.84.1.75; helo=l2mail1.panix.com; envelope-from=context@rik.users.panix.com; receiver= X-Greylist: delayed 939 seconds by postgrey-1.36 at zapf.ntg.nl; Sun, 24 Jan 2021 05:28:46 CET Original-Received: from l2mail1.panix.com (l2mail1.panix.com [166.84.1.75]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) (No client certificate requested) by zapf.ntg.nl (Postfix) with ESMTPS id 69D611C15B9 for ; Sun, 24 Jan 2021 05:28:46 +0100 (CET) Original-Received: from mailbackend.panix.com (mailbackend.panix.com [166.84.1.89]) by l2mail1.panix.com (Postfix) with ESMTPS id 4DNfjw1lHhzDRF for ; Sat, 23 Jan 2021 23:13:08 -0500 (EST) Original-Received: from [192.168.0.13] (cpe-24-194-28-156.nycap.res.rr.com [24.194.28.156]) by mailbackend.panix.com (Postfix) with ESMTPSA id 4DNfjs13WszZN5 for ; Sat, 23 Jan 2021 23:13:05 -0500 (EST) Content-Language: en-US X-BeenThere: ntg-context@ntg.nl X-Mailman-Version: 2.1.26 Precedence: list List-Id: mailing list for ConTeXt users List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: ntg-context-bounces@ntg.nl Original-Sender: "ntg-context" Xref: news.gmane.io gmane.comp.tex.context:110359 Archived-At: This is a multi-part message in MIME format. --===============2745813434971211576== Content-Type: multipart/alternative; boundary="------------C3D7D2BD1979BC0446E5BC33" Content-Language: en-US This is a multi-part message in MIME format. --------------C3D7D2BD1979BC0446E5BC33 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Hans and all, Preparing my standard environments for future strict enforcement of overloading prevention, I have run into one issue. I had been using the following construction to change the formatting of URLs: \let\OrigHyphenatedurl\hyphenatedurl \starttexdefinition hyphenatedurl #URL   \begingroup     \URLfont\OrigHyphenatedurl{#URL}   \endgroup \stoptexdefinition This results in the following warning about overloading \hyphenatedurl: csname overload > warning, protection level 3, control sequence 'hyphenatedurl', properties 'permanent protected', file 'env_layout.mkvi', line 1 I have tried adding \overloaded to indicate the intentional overloading, but \overloaded cannot be used with \starttexdefinition, so I rewrote it as: \let\OrigHyphenatedurl\hyphenatedurl \overloaded\define[1]\hyphenatedurl{%   \begingroup%     \URLfont\OrigHyphenatedurl{#1}%   \endgroup}% but that (and also with \overloaded\def\hyphenatedurl#1...) gives the same (except for the line number) warning: csname overload > warning, protection level 3, control sequence 'hyphenatedurl', properties 'permanent protected', file 'env_layout.mkvi', line 822 So, what is the proper way to indicate intentional overloading? Or should this redefinition be done in another way? (Also, it is interesting that the line number in the first warning message does not point to the actual line.) -- Rik --------------C3D7D2BD1979BC0446E5BC33 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit

Hans and all,

Preparing my standard environments for future strict enforcement of overloading prevention, I have run into one issue.

I had been using the following construction to change the formatting of URLs:

\let\OrigHyphenatedurl\hyphenatedurl
\starttexdefinition hyphenatedurl #URL
  \begingroup
    \URLfont\OrigHyphenatedurl{#URL}
  \endgroup
\stoptexdefinition

This results in the following warning about overloading \hyphenatedurl:

csname overload > warning, protection level 3, control sequence 'hyphenatedurl', properties 'permanent protected', file 'env_layout.mkvi', line 1

I have tried adding \overloaded to indicate the intentional overloading, but \overloaded cannot be used with \starttexdefinition, so I rewrote it as:

\let\OrigHyphenatedurl\hyphenatedurl
\overloaded\define[1]\hyphenatedurl{%
  \begingroup%
    \URLfont\OrigHyphenatedurl{#1}%
  \endgroup}%

but that (and also with \overloaded\def\hyphenatedurl#1...) gives the same (except for the line number) warning:

csname overload > warning, protection level 3, control sequence 'hyphenatedurl', properties 'permanent protected', file 'env_layout.mkvi', line 822

So, what is the proper way to indicate intentional overloading? Or should this redefinition be done in another way?

(Also, it is interesting that the line number in the first warning message does not point to the actual line.)

--
Rik

--------------C3D7D2BD1979BC0446E5BC33-- --===============2745813434971211576== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX18KSWYgeW91ciBxdWVzdGlvbiBpcyBvZiBpbnRlcmVz dCB0byBvdGhlcnMgYXMgd2VsbCwgcGxlYXNlIGFkZCBhbiBlbnRyeSB0byB0aGUgV2lraSEKCm1h aWxsaXN0IDogbnRnLWNvbnRleHRAbnRnLm5sIC8gaHR0cDovL3d3dy5udGcubmwvbWFpbG1hbi9s aXN0aW5mby9udGctY29udGV4dAp3ZWJwYWdlICA6IGh0dHA6Ly93d3cucHJhZ21hLWFkZS5ubCAv IGh0dHA6Ly9jb250ZXh0LmFhbmhldC5uZXQKYXJjaGl2ZSAgOiBodHRwczovL2JpdGJ1Y2tldC5v cmcvcGhnL2NvbnRleHQtbWlycm9yL2NvbW1pdHMvCndpa2kgICAgIDogaHR0cDovL2NvbnRleHRn YXJkZW4ubmV0Cl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fCg== --===============2745813434971211576==--