Follow-up Comment #10, bug #67372 (group groff): [comment #7 comment #7:]
> I should add that I am concerned that it's impossible to intelligently and
> coherently maintain the concept of "interpolation depth" (or "input level")
> when the parser state has encountered the escape function selector and is
> expecting a delimiter. Interpolating the delimiter with a `\*` interpolation
> necessarily implies performing an interpolation and therefore increasing the
> depth, which defeats the whole purpose of having an interpolation depth in
> the first place.
This statement was not coherent. Let me try that again.
Using the `\*` escape sequence to interpolate the delimiter of an escape
sequence necessarily means performing an interpolation, and therefore
increasing the interpolation depth. I think that suppressing the increase of
interpolation depth in this case, as one might propose, would make GNU
_troff_'s (non-compatibility-mode) grammar less consistent and defeat the
purpose of tracking the interpolation depth in the first place.
> It may therefore be necessary to "ban" string interpolations when the
> formatter expects an opening delimiter on the input stream.
I consequently think the foregoing follows.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?67372>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
signature.asc
Description: PGP signature
