Follow-up Comment #9, bug #68022 (group groff): At 2026-02-07T15:50:15-0500, Dave wrote: > Follow-up Comment #8, bug #68022 (group groff): > > [comment #7 comment #7:] >> I'd split the hair differently. It's a code change because it >> changes a file that is compiled/interpreted, and things like >> accidental semicolon omission can occur and wreck stuff. > > I should have more specifically said it changes no code _syntax_, not > just no code logic. No way to mess up the parsing if you're not > changing anything syntactical to the interpreter.
That's true, but accidents can happen, and computational grammar is not
unknown in diagnostic messages (not applicable here, I grant).
On the other hand, we have "smoke tests" to catch this sort of thing,
though again, that's not applicable here, because _gropdf_ gets
extensive exercise in any groff build, in generation of our own docs.
>> But, there's no code freeze on Perl code
>
> Sorry if I was unclear: I meant this only in terms of classifying the
> bug as "Documentation" or "Feature change," not in terms of code
> freezes.
Ahh. I agree with leaving it as "Documentation". The _feature_ has
already landed without a Savannah ticket; we're just trying to solidify
it for release at this point.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?68022>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
signature.asc
Description: PGP signature
