[Bug libc/30371] C2x strtol binary constant handling is incomplete

["bruno at clisp dot org" <sourceware-bugzilla@sourceware.org>]

https://sourceware.org/bugzilla/show_bug.cgi?id=30371

--- Comment #3 from Bruno Haible <bruno at clisp dot org> ---
(In reply to Eric Blake from comment #1)
> Note that C2X has not yet decided what to do about strto*l parsing with a
> binary prefix.  ... This is a
> SILENT change in runtime behavior, based on which version of the standard
> you build against.

Yes, but the fact that it's a change in runtime behaviour is handled by the
introduction of __isoc23_strto*, __isoc23_wcsto* in Joseph Myers' patch
https://sourceware.org/git/?p=glibc.git;a=commitdiff;h=64924422a99690d147a166b4de3103f3bf3eaf6c
.

If "Rejected" (as in comment #2) means that the final ISO C 23 will have the
same wording as https://www.open-std.org/jtc1/sc22/wg14/www/docs/n3088.pdf (the
latest draft from 2023-01-24), then the wording there (§ 7.24.1.7, page 358 =
377/757) means that when parsing the input string "0b", only one character
shall be consumed, like for the input string "0x". That is what this BZ and its
proposed patch are about.

> The final version of C2X may state something different than in the draft,
> and glibc may have to course-correct yet again.

True. But it's very unlikely that the final version of C2X will specify that in
when parsing "0b" two characters shall be consumed, while when parsing "0x"
only one character shall be consumed.

-- 
You are receiving this mail because:
You are on the CC list for the bug.