Follow-up Comment #17, bug #67571 (group groff): At 2025-11-17T15:05:33-0500, Dave wrote: > Follow-up Comment #16, bug #67571 (group groff): > > [comment #15 comment #15:] >> commit 7e9e9260244ed1a551ea9663124841ac7861b97d > > (For the record, this commit has not been pushed.)
Agreed and acknowledged.
>> an attempt to interpolate a character class as a "title part"
>> results in undesired code flow.
>
> As this is documented as unsupported usage, undefined behavior seems a
> reasonable result.
Yes, but I don't like it, especially when it's not diagnosed. I'm work
up a commit to do precisely that.
In fact I suppose that's what this global Boolean
`using_character_classes` is actually for--to kick the parser into a
special state so that it interprets special character tokens differently
just for this one request.
I strongly dislike that from a design perspective.
> "Currently, only the 'cflags' request can handle references to
> character classes," says the manual.
But the `class` request itself must be able to as well, or there's no
point having any code referring to nested classes.
Or maybe nested classes don't actually work, and we've been carrying
dead weight for 15 years.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?67571>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
signature.asc
Description: PGP signature
