Follow-up Comment #7, bug #68908 (group groff): Hmm. The .Y bug itself might not be new; it might have only become recently exposed by the way version strings are generated. Trawling some old builds I had lying around, I found versions of the form:
GNU groff version 1.23.0.rc4.19-96b92-dirty
GNU groff version 1.24.0.8-7152a-modified
GNU groff version 1.24.1.1050-96092-modified
GNU groff version 1.25.0.rc1.54-741f-modified
Notably, all of these put a dot after the third element, before tacking on all
the build-specific stuff. "version 1.25.0-modified" breaks that tradition,
perhaps exposing a lurking bug wherein the code populating the .Y register
stopped reading at a dot or end of string, but read everything it encountered
otherwise.
This suggests that the underlying structural issue is that "number" registers
are not stored in numeric data types. This is perhaps understandable given
the Frankenstein existence of the "string-valued register," but this
compromise seems to trade some coding convenience for less type safety. (A
condition that has never otherwise arisen in the history of C/C++ code!)
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?68908>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
signature.asc
Description: PGP signature
