From: Andreas Schwab <schwab@linux-m68k.org>
To: Florian Weimer via Libc-alpha <libc-alpha@sourceware.org>
Cc: Carlos O'Donell <carlos@redhat.com>,
Florian Weimer <fweimer@redhat.com>
Subject: Re: [PATCH 1/2] localedef: Fix handling of empty mon_decimal_point
Date: Mon, 31 Jan 2022 17:09:41 +0100 [thread overview]
Message-ID: <87ee4n6g56.fsf@igel.home> (raw)
In-Reply-To: <87bkzs7wp1.fsf@oldenburg.str.redhat.com> (Florian Weimer via Libc-alpha's message of "Mon, 31 Jan 2022 16:26:50 +0100")
On Jan 31 2022, Florian Weimer via Libc-alpha wrote:
> There's an existing comment
>
> /* The decimal point must not be empty. This is not said explicitly
> in POSIX but ANSI C (ISO/IEC 9899) says in 4.4.2.1 it has to be
> != "". */
>
> that says that empty strings/null characters are invalid.
This is only about decimal_point, mon_decimal_point can be empty.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
next prev parent reply other threads:[~2022-01-31 16:09 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-31 5:34 [PATCH 0/2] Make C/POSIX and C.UTF-8 consistent Carlos O'Donell
2022-01-31 5:34 ` [PATCH 1/2] localedef: Fix handling of empty mon_decimal_point Carlos O'Donell
2022-01-31 15:26 ` Florian Weimer
2022-01-31 16:09 ` Andreas Schwab [this message]
2022-01-31 16:20 ` Florian Weimer
2022-01-31 16:30 ` Andreas Schwab
2022-01-31 16:37 ` Florian Weimer
2022-02-01 11:47 ` Florian Weimer
2022-02-01 16:00 ` Carlos O'Donell
2022-02-01 16:14 ` Carlos O'Donell
2022-01-31 5:34 ` [PATCH 2/2] localedata: Adjust C.UTF-8 to align with C/POSIX Carlos O'Donell
2022-01-31 8:47 ` Andreas Schwab
2022-01-31 16:07 ` Carlos O'Donell
2022-02-01 12:05 ` Florian Weimer
2022-02-01 16:13 ` Carlos O'Donell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ee4n6g56.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=carlos@redhat.com \
--cc=fweimer@redhat.com \
--cc=libc-alpha@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).