C++ Logo

SG16

Advanced search

Subject: Re: [ WG14 ] Mixed Wide String Literals
From: Corentin Jabot (corentinjabot_at_[hidden])
Date: 2020-12-07 02:50:32


On Mon, 7 Dec 2020 at 09:43, Philipp Klaus Krause via SG16 <
sg16_at_[hidden]> wrote:

> Am 06.12.20 um 23:41 schrieb Tom Honermann via SG16:
>
> > * WG14: Improve support for Unicode characters in identifiers
> > <https://github.com/sg16-unicode/sg16/issues/56>
>
> Will there be problems for EBCDIC systems? AFAIK, C++ dropped support
> for EBCDIC the moment there was no IBM representative in WG14. But C
> still supports it.
>

Unicode identifiers happen in C++ after phase 1 and so neither the source
encoding nor the execution encoding are impacted.

>
> Philipp
>
> P.S.: A related topic, but far less ambitious: Would it make sense to
> add @ and $ to the basic source character set
> (http://www.colecovision.eu/stuff/proposal-basic-@.html)? AFAIK, this
> should work for implementations that use ASCII (or an extension, such as
> UTF-8) as well as those that use an EBCDIC code page that can be used
> for C programming today.
>

It's actually more ambitious I am afraid. This question is asked
frequently in WG21 and 2 arguments against it are

@ is used by objective-c(++) and $ is 1/valid in identifiers in some gcc
implementation extension 2/ used by code generators.

(On a personal note, I think $ would be useful for e.g reflection syntaxes
but that is an uphill battle!)

> --
> SG16 mailing list
> SG16_at_[hidden]
> https://lists.isocpp.org/mailman/listinfo.cgi/sg16
>



SG16 list run by sg16-owner@lists.isocpp.org