On Thu, 26 Sep 2019, Eric Botcazou wrote:
> > For C, I think such UCNs violate the Semantics but not the Constraints on
> > UCNs, so no diagnostic is actually required in C, although it is permitted
> > as a pedwarn / error.
> >
> > However, while C++ doesn't have that Semantics / Constraints div
> For C, I think such UCNs violate the Semantics but not the Constraints on
> UCNs, so no diagnostic is actually required in C, although it is permitted
> as a pedwarn / error.
>
> However, while C++ doesn't have that Semantics / Constraints division,
> it's also the case that before C++2a, C++ on
On Tue, 24 Sep 2019, Eric Botcazou wrote:
> > I think this has to depend on the C standards version. I think each C
> > standard needs to be read against the edition of ISO 10646 current at
> > the time of standards approval (the references are sadly not
> > versioned, so the version is implied).
On Tue, 24 Sep 2019, Eric Botcazou wrote:
> Hi,
>
> the Universal Character Names accepted by the C family of compilers are
> mapped
> to those of ISO/IEC 10646, which defines the Universal Character Set
> codespace
> as the range 0-0x10 inclusive. The upper bound is already enforced for
On Tue, 24 Sep 2019, Florian Weimer wrote:
> I think this has to depend on the C standards version. I think each C
> standard needs to be read against the edition of ISO 10646 current at
> the time of standards approval (the references are sadly not
> versioned, so the version is implied). Early
> I think this has to depend on the C standards version. I think each C
> standard needs to be read against the edition of ISO 10646 current at
> the time of standards approval (the references are sadly not
> versioned, so the version is implied). Early versions of ISO 10646
> definitely do not h
* Eric Botcazou:
> the Universal Character Names accepted by the C family of compilers
> are mapped to those of ISO/IEC 10646, which defines the Universal
> Character Set codespace as the range 0-0x10 inclusive. The
> upper bound is already enforced for identifiers but not for
> literals, so
Hi,
the Universal Character Names accepted by the C family of compilers are mapped
to those of ISO/IEC 10646, which defines the Universal Character Set codespace
as the range 0-0x10 inclusive. The upper bound is already enforced for
identifiers but not for literals, so the following code i
