On 6/13/2023 12:43 PM, Hans van der Meer via ntg-context wrote:
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.
there
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
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:
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.
> On 12 Jun 2023, at 11:12, Hans Hagen via ntg-context
> 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
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
