Follow-up Comment #5, bug #61100 (project groff):
[comment #4 comment #4:]
>
> @code{de} defines a macro that inherits the compatibility mode
> enablement status of its context (@pxref{Implementation Differences}).
>
The above seems to say that the defined macro runs in the compatibility state
in which it is invoked, while...
>
> compatibility mode needs to be switched off while such a macro is
> interpreted---without disturbing that state when it is finished.
>
...this seems to say the defined macro runs in a fixed compatibility state
regardless of that of its invoker.
The problem may be the overloading of the word "context"? Its second
appearance specifically says "callable from contexts where...," so it's clear
this is talking about the invoker's context. The first instance may be
talking instead about the context in which the macro is _defined_ rather than
that in which it is invoked. That at least lets me mentally reconcile the
above two quoted passages, but I'm not sure if it's the correct reading. (I
have little real-world experience with using compatibility mode, so much about
it remains mysterious to me.)
I may be getting us lost in the weeds re: this bug's topic, so feel free to
redirect this discussion to the email list or other alternate venue.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?61100>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
