From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-0.7 required=5.0 tests=DKIM_INVALID,DKIM_SIGNED, HTML_MESSAGE,MAILING_LIST_MULTI,T_SCC_BODY_TEXT_LINE,URIBL_SBL_A autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 3420 invoked from network); 13 Jun 2023 10:44:11 -0000 Received: from zapf.ntg.nl (5.39.185.232) by inbox.vuxu.org with ESMTPUTF8; 13 Jun 2023 10:44:11 -0000 Received: from localhost (localhost [127.0.0.1]) by zapf.ntg.nl (Postfix) with ESMTP id 7F9CBBC4; Tue, 13 Jun 2023 12:43:46 +0200 (CEST) X-Virus-Scanned: Debian amavisd-new at zapf.ntg.nl 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 v7egjP9EWdUz; Tue, 13 Jun 2023 12:43:42 +0200 (CEST) Received: from zapf.ntg.nl (localhost [127.0.0.1]) by zapf.ntg.nl (Postfix) with ESMTP id 5905D720E; Tue, 13 Jun 2023 12:43:42 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by zapf.ntg.nl (Postfix) with ESMTP id 10E34720E for ; Tue, 13 Jun 2023 12:43:41 +0200 (CEST) X-Virus-Scanned: Debian amavisd-new at zapf.ntg.nl 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 ktesuygqzbHA for ; Tue, 13 Jun 2023 12:43:37 +0200 (CEST) Received-SPF: Pass (mailfrom) identity=mailfrom; client-ip=212.54.42.168; helo=smtpq5.tb.mail.iss.as9143.net; envelope-from=havdmeer@ziggo.nl; receiver= Received: from smtpq5.tb.mail.iss.as9143.net (smtpq5.tb.mail.iss.as9143.net [212.54.42.168]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by zapf.ntg.nl (Postfix) with ESMTPS id 7E94BBC4 for ; Tue, 13 Jun 2023 12:43:37 +0200 (CEST) Received: from [212.54.42.106] (helo=smtp2.tb.mail.iss.as9143.net) by smtpq5.tb.mail.iss.as9143.net with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1q91Uu-0004vJ-88 for ntg-context@ntg.nl; Tue, 13 Jun 2023 12:43:36 +0200 Received: from smtpclient.apple ([84.104.102.59]) by smtp2.tb.mail.iss.as9143.net with ESMTPA id 91UtqEKZGkLm091Uuq1kfx; Tue, 13 Jun 2023 12:43:36 +0200 X-Env-Mailfrom: havdmeer@ziggo.nl X-Env-Rcptto: ntg-context@ntg.nl X-SourceIP: 84.104.102.59 X-CNFS-Analysis: v=2.4 cv=Utqldc8B c=1 sm=1 tr=0 ts=64884858 cx=a_exe a=r8aFSP8g8qyxuwAfcqn69g==:117 a=r8aFSP8g8qyxuwAfcqn69g==:17 a=MiNTnEJAAAAA:8 a=YEMqx4UAAAAA:8 a=Uows8UApAAAA:8 a=ACQCx6kCAAAA:8 a=xtERp6CFAAAA:8 a=a3nu-2BBAAAA:8 a=6k79Cg5rk3SlKJo6AZkA:9 a=QEXdDO2ut3YA:10 a=Hy-_uf8gNFIMv20pj70A:9 a=n3VMYFBQA7sYol-S:21 a=_W_S_7VecoQA:10 a=LmrbSfiT3hecnSZifb5M:22 a=V0662LiR8DSfwiDagK97:22 a=oX0v64vK4IwbpfTCMRm2:22 a=Sab0UneHBzlWrQDlOuxD:22 a=ekCXXmE-vB8RPiJ3MEZb:22 X-Authenticated-Sender: havdmeer@ziggo.nl DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ziggo.nl; s=202002corplgsmtpnl; t=1686653016; bh=whXFJgEq5vpM26hTPIsxngc8Jojhk9JZJsrgSdkUTs0=; h=From:Subject:Date:References:To:In-Reply-To; b=DFbpqOFabJp3111ZGWIzwor8PxG08zMdAigv6rbkQyQkmMbHim87zbf90tjL97P98 m+3vIgTHFuNM7GfJAtE6UwLhv5tHaDA3y5VPpgz+dp9HGtGB3mwxsj18qheraHvGKV qGICtiJW9JWTd6KXIXUk9pOdh/xR+liEKaPfEH0Hxat7wDfq+G/FgQztuRctbQMGwQ 3AhWFmOUy1UgPrqxoFxxE6kqg5uqomoP5gUYFiiaWqEwb3Re3tyMjEOyHvUFiARGOV qq2xiG0UTty6yRGXaYRNaldq1BPkJt9yQ3WSRNcL5xtb5GCi8YTAPUqL4h4mUlYdFb nrqkuOKJe9eCA== Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.600.7\)) Date: Tue, 13 Jun 2023 12:43:25 +0200 References: <80A4DB81-41CB-4D3D-9A53-09A4DED5E665@ziggo.nl> <09bf23d1-0e29-005b-ad2b-75bc836d299a@freedom.nl> <52D03A0F-C7EE-4AD3-8372-646CEDAD8AEE@ziggo.nl> <2ea4e304-c79c-eaa4-6abf-f1f6897c446f@freedom.nl> To: NTG ConTeXt In-Reply-To: <2ea4e304-c79c-eaa4-6abf-f1f6897c446f@freedom.nl> Message-Id: X-Mailer: Apple Mail (2.3731.600.7) X-CMAE-Envelope: MS4xfIV+EgxId9/z9s3cRUOdKqeGXAdOCX/MUFYajpD+UNgDCseKzHB1Dy2EK8XYtqhzjcxOv0E/oOsT334a4r0PKONEcHi+qLvbzj3/9xTpW/xcGj3JPkLC 1fOkHidK0uYFjJyphp1EwBZPlUgjGRP9gJFyaQC1j2I3MDdRarKmzXxaUG/G2fAY1NtnA5UchKLs7w== Subject: Re: [NTG-context] letfrozen? X-BeenThere: ntg-context@ntg.nl X-Mailman-Version: 2.1.38 Precedence: list List-Id: mailing list for ConTeXt users List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Hans van der Meer via ntg-context Reply-To: mailing list for ConTeXt users Cc: Hans van der Meer Content-Type: multipart/mixed; boundary="===============5926098456759121346==" Errors-To: ntg-context-bounces@ntg.nl Sender: "ntg-context" --===============5926098456759121346== Content-Type: multipart/alternative; boundary="Apple-Mail=_BE11FF1D-35CC-43B4-9DBB-4E8EB80A66AC" --Apple-Mail=_BE11FF1D-35CC-43B4-9DBB-4E8EB80A66AC Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 Of course. But without that \enabledirective I can redefine the frozen = macro at will, as a simple test did show. The crux, however, is that one wants to protect the frozen code always, = irrespective of that directive setting. dr. Hans van der Meer > On 12 Jun 2023, at 19:47, Hans Hagen via ntg-context = wrote: >=20 > On 6/12/2023 12:32 PM, Hans van der Meer via ntg-context wrote: >>> On 12 Jun 2023, at 11:12, Hans Hagen via ntg-context = wrote: >>>=20 >>> On 6/12/2023 10:57 AM, Hans van der Meer via ntg-context wrote: >>>> The manual LMTX-primitives on page 21 tells me: >>>> You can explicitly freeze an unfrozen macro. >>>> ... >>>> A redefinition will now give: You can't redefine a frozen macro. >>>> But is this true? The following code seems to contradict this: >>>> \def\HOME{myhome} >>>> \writestatus{1}{\meaning\HOME} >>>> \letfrozen\HOME >>>> \writestatus{2}{\meaning\HOME} >>>> \def\HOME{other home} >>>> \writestatus{3}{\meaning\HOME} >>>> =EF=BF=BC >>>> Is this mechanism broken? It looks so useful to prevent accidental = redefinition! >>>=20 >>> here i run with >>>=20 >>> \enabledirectives[overloadmode=3Derror] >>>=20 >>> (you can do that in cont-sys.mkxl) >>>=20 >>> \enabledirectives[overloadmode=3Dwarning] >>> Hans >>>=20 >> Pity. Now I get on loading the tex file: >> "csname overload > fatal error, protection level 4, control sequence = 'nbsp', properties 'immutable', file 't-hvdm-text.tex', line 63 >> while I had hoped that frozen would give me something like: >> illegal attempt to redefine \HOME >> Byproduct (not unwanted) the above illegal redefinition to be solved = :-) >> May I ask why obviously the frozen-mechanism seems (yet?) = unimplemented? > It's okay and has been around for quite a while now. >=20 > \enabledirectives[overloadmode=3Derror] >=20 > \starttext >=20 > \frozen\def\HOME{!!!!} >=20 > \def\HOME{!!!!!} >=20 > \stoptext >=20 >=20 > ----------------------------------------------------------------- > Hans Hagen | PRAGMA ADE > Ridderstraat 27 | 8061 GH Hasselt | The Netherlands > tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl > ----------------------------------------------------------------- >=20 > = __________________________________________________________________________= _________ > If your question is of interest to others as well, please add an entry = to the Wiki! >=20 > maillist : ntg-context@ntg.nl / = https://www.ntg.nl/mailman/listinfo/ntg-context > webpage : https://www.pragma-ade.nl / http://context.aanhet.net > archive : https://bitbucket.org/phg/context-mirror/commits/ > wiki : https://contextgarden.net > = __________________________________________________________________________= _________ --Apple-Mail=_BE11FF1D-35CC-43B4-9DBB-4E8EB80A66AC Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8
Of = course. But without that \enabledirective I can redefine the frozen = macro at will, as a simple test did show.
The crux, however, = is that one wants to protect the frozen code always, irrespective of = that directive setting.

dr. Hans van der = Meer
On 12 Jun 2023, at = 19:47, Hans Hagen via ntg-context <ntg-context@ntg.nl> = wrote:

On = 6/12/2023 12:32 PM, Hans van der Meer via ntg-context = wrote:
On 12 Jun = 2023, at 11:12, Hans Hagen via ntg-context <ntg-context@ntg.nl> = wrote:

On 6/12/2023 10:57 AM, Hans van der Meer via ntg-context = wrote:
The manual LMTX-primitives on page = 21 tells me:
= You can explicitly freeze an unfrozen macro.
= ...
= A redefinition will now give: You can't redefine a frozen = macro.
But is this true? The following code seems to contradict = this:
\def\HOME{myhome}
\writestatus{1}{\meaning\HOME}
\letfrozen= \HOME
\writestatus{2}{\meaning\HOME}
\def\HOME{other = home}
\writestatus{3}{\meaning\HOME}
=EF=BF=BC
Is this = mechanism broken? It looks so useful to prevent accidental = redefinition!

here i run = with

\enabledirectives[overloadmode=3Derror]

(you can do = that in = cont-sys.mkxl)

\enabledirectives[overloadmode=3Dwarning]
Hans
Pity. Now I get on loading the tex file:
"csname = overload > fatal error, protection level 4, control sequence 'nbsp', = properties 'immutable', file 't-hvdm-text.tex', line 63
while I had = hoped that frozen would give me something like:
illegal attempt to = redefine \HOME
Byproduct (not unwanted) the above illegal = redefinition to be solved :-)
May I ask why obviously the = frozen-mechanism seems (yet?) unimplemented?
It's okay = and has been around for quite a while = now.

\enabledirectives[overloadmode=3Derror]

\starttext
<= br>    \frozen\def\HOME{!!!!}

=    \def\HOME{!!!!!}

\stoptext


-----------= ------------------------------------------------------
=             &n= bsp;           &nbs= p;            =     Hans Hagen | PRAGMA ADE
=             &n= bsp;Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
=       tel: 038 477 53 69 | = www.pragma-ade.nl | = www.pragma-pod.nl
-----------------------------------------------------= ------------

______________________________________________________= _____________________________
If your question is of interest to = others as well, please add an entry to the Wiki!

maillist : = ntg-context@ntg.nl / = https://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : = https://www.pragma-ade.nl / http://context.aanhet.net
archive  : = https://bitbucket.org/phg/context-mirror/commits/
wiki =     : = https://contextgarden.net
_____________________________________________= ______________________________________
<= br>= --Apple-Mail=_BE11FF1D-35CC-43B4-9DBB-4E8EB80A66AC-- --===============5926098456759121346== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline ___________________________________________________________________________________ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context webpage : https://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : https://contextgarden.net ___________________________________________________________________________________ --===============5926098456759121346==--