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). Early versions of ISO 10646 > > definitely do not have the codespace restriction you mention. > > Note the already existing hardcoded check in ucn_valid_in_identifier though.
No C or C++ standard version allows characters outside that range in identifiers, so that check is independent of the ISO 10646 version being used. -- Joseph S. Myers jos...@codesourcery.com
