From: Alejandro Colomar <alx.manpages@gmail.com>
To: Brian.Inglis@Shaw.ca, linux-man@vger.kernel.org
Cc: Jakub Wilk <jwilk@jwilk.net>, Tom Schwindl <schwindl@posteo.de>
Subject: Re: Using C23 digit separators not locale digit grouping characters
Date: Thu, 9 Feb 2023 13:47:23 +0100 [thread overview]
Message-ID: <b5abf56a-23f0-0aa7-1028-e08145a42e24@gmail.com> (raw)
In-Reply-To: <0a6773fa-257e-ed5c-f951-39a0876b9dcb@Shaw.ca>
[-- Attachment #1.1: Type: text/plain, Size: 1262 bytes --]
Hi Brian,
On 2/8/23 23:10, Brian Inglis wrote:
> See discussion 10 years ago in WG21 C++:
>
> https://open-std.org/jtc1/sc22/wg21/docs/papers/2013/n3499.html
>
> where ambiguity with C++ user-defined literal unit operators and "_" was an
> issue, and Objective C/C++ parsing problems with using whitespace.
Interesting. Let it be a ' then.
>
> So in 2020 WG14 C, opting for compatibility with WG21 C++; quoting:
>
> Prior Art: C++, Intel ICC, EDG, Microsoft Visual Studio
> in
> https://www.open-std.org/JTC1/SC22/WG14/www/docs/n2606.pdf
> https://www.open-std.org/JTC1/sc22/wg14/www/docs/n2626.pdf
>
> FYI see comment in:
>
> https://thephd.dev/c-the-improvements-june-september-virtual-c-meeting
>
> "Guess who uses apostrophes for digit separators! The SWISS! And who is in
> Switzerland? ISO! I see WG14 is no less corrupt than WG21.
> — Miro Knejp" ;^>
I remember having read that :D
>
> We are going to be seeing these used a lot in future from GCC , and as man-pages
> are immersed in a sea of C, we might as well start getting used to it, which is
> why I made that suggestion.
Agree.
--
<http://www.alejandro-colomar.es/>
GPG key fingerprint: A9348594CE31283A826FBDD8D57633D441E25BB5
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-02-09 12:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-28 20:40 Using C23 digit separators not locale digit grouping characters Brian Inglis
2023-01-29 14:38 ` Alejandro Colomar
2023-01-29 21:04 ` Brian Inglis
2023-01-29 21:19 ` Alejandro Colomar
2023-02-02 22:29 ` Brian Inglis
2023-02-02 23:59 ` Alejandro Colomar
2023-02-03 13:27 ` Tom Schwindl
2023-02-05 13:47 ` Alejandro Colomar
2023-02-08 21:00 ` Jakub Wilk
2023-02-08 21:06 ` Alejandro Colomar
2023-02-08 22:10 ` Brian Inglis
2023-02-09 12:47 ` Alejandro Colomar [this message]
2023-02-04 7:19 ` Brian Inglis
2023-02-05 13:32 ` Alejandro Colomar
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=b5abf56a-23f0-0aa7-1028-e08145a42e24@gmail.com \
--to=alx.manpages@gmail.com \
--cc=Brian.Inglis@Shaw.ca \
--cc=jwilk@jwilk.net \
--cc=linux-man@vger.kernel.org \
--cc=schwindl@posteo.de \
/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