URL: <https://savannah.gnu.org/bugs/?67735>
Summary: [long-term] use "unsigned char" for troff's internal
character type with militant consistency
Group: GNU roff
Submitter: gbranden
Submitted: Tue 25 Nov 2025 05:08:24 PM UTC
Category: Core
Severity: 3 - Normal
Item Group: Lint
Status: In Progress
Privacy: Public
Assigned to: gbranden
Open/Closed: Open
Discussion Lock: Any
Planned Release: None
_______________________________________________________
Follow-up Comments:
-------------------------------------------------------
Date: Tue 25 Nov 2025 05:08:24 PM UTC By: G. Branden Robinson <gbranden>
"unsigned char" appears to already be used in a preponderance of cases, and
increasingly with recent code changes of mine, but there's still a lot of
punning to the C "char"s of undefined signedness.
It's necessary to nail this down to migrate the underlying representation type
to something wide enough to hold Unicode code points. And that in turn is
necessary for resolution of bug #40720.
Perhaps we could pivot through `typedef grochar unsigned char;`.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?67735>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
signature.asc
Description: PGP signature
