Path: csiph.com!eternal-september.org!feeder.eternal-september.org!reader01.eternal-september.org!.POSTED!not-for-mail From: Tim Rentsch Newsgroups: comp.lang.c Subject: Re: Unicode in C Sources Date: Wed, 19 Feb 2020 12:30:01 -0800 Organization: A noiseless patient Spider Lines: 17 Message-ID: <86d0aae2wm.fsf@linuxsc.com> References: <87h80axl7s.fsf@bsb.me.uk> <5ajZF.602301$CO7.252756@fx36.am4> <341090e3-1f1b-47bf-aded-7337c29f3692@googlegroups.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Injection-Info: reader02.eternal-september.org; posting-host="24fb35cc0bcbe230f7108cd93f73ffe7"; logging-data="30894"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX18nhii66MOug0SpOSJzt2zKfPYAa+Y10N0=" User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.4 (gnu/linux) Cancel-Lock: sha1:kMQtTFAiqLCFGQrr7+eowt9x0DI= sha1:npWi5pm9Dhb+1Euk/kHSjKZC5tg= Xref: csiph.com comp.lang.c:150085 James Kuyper writes: > No, it seems clear to me that "extended identifier" refers to > identifiers containing members of the extended character set - NOT > UCNs. That is highly unlikely. Extended characters in identifiers are not required in any implementation, and what's more, implementations have always been allowed to use extended characters in identifiers, because in C89/C90 any character (outside of a string constant, etc) not in the basic character set implies undefined behavior. There is no point in calling something out as an addition if nothing has been added. What C99 added, with the syntax for identifiers requiring UCNs to be supported, is a way of using characters outside the basic character set in a way that is /guaranteed to be portable/. It is thus much more likely that the phrase "extended identifiers" used in the Standard refers to UCNs in idenfiers, not extended characters.