C++ Logo

SG16

Advanced search

Subject: Re: Characters literals in preprocessor conditionals
From: Corentin Jabot (corentinjabot_at_[hidden])
Date: 2020-06-12 04:00:34


On Thu, Jun 11, 2020, 18:00 Thiago Macieira via SG16 <sg16_at_[hidden]>
wrote:

> On Thursday, 11 June 2020 08:53:56 PDT Tom Honermann via SG16 wrote:
> > Agreed. It would be interesting to know if WG14 members have some
> > historical perspective on this being implementation-defined. Perhaps
> > Aaron can assist in getting an answer to that question. Copying the
> > liason list...
>
> Could be an ASCII-encoded source file being compiled to EBCDIC or
> vice-versa.
> The preprocessor would run in the encoding of the source file, but the
> actual
> compiler would translate into the execution character set, which won't
> match
> the source character set.
>

The source character set shouldn't matter as long as it is properly deduced.
I guess it's more of an issue for tooling that do not have an execution
encoding at all. But it doesn't appear to be an issue in practice.

>
> Helps with writing source code without the need for digraphs or trigraphs.
>
> --
> Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org
> Software Architect - Intel System Software Products
>
>
>
> --
> SG16 mailing list
> SG16_at_[hidden]
> https://lists.isocpp.org/mailman/listinfo.cgi/sg16
>



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