This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug preprocessor/9449] UCNs not recognized in identifiers (c++/c99)
- From: "joseph at codesourcery dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 22 Feb 2005 02:13:59 -0000
- Subject: [Bug preprocessor/9449] UCNs not recognized in identifiers (c++/c99)
- References: <20030127145600.9449.rearnsha@arm.com>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Additional Comments From joseph at codesourcery dot com 2005-02-22 02:13 -------
Subject: Re: UCNs not recognized in identifiers
(c++/c99)
On Mon, 21 Feb 2005, zack at codesourcery dot com wrote:
> Standing policy is that all cases which provoke undefined behavior
> inside the preprocessor, except already-documented GNU extensions,
> shall produce hard errors. I am tempted to make a partial exception
Which policy (cf. bug 14634) I agree with. However, I don't think there
should be any exception made. The standards (C99 and C++03) are
implementable as-is. They have oddities; some of these may be suitable
for submission as DRs, and if the committees fix them in a TC rather than
a major new standard revision then we no longer need implement those
oddities, but for now the standard says what it says. The headings in C99
Annex D are except for "Digits" irrelevant to the normative requirements;
anything in "Digits" is a UCN for a digit, whether or not it appears
elsewhere. (C++03 corrected the typo in C++98 which was noted in C++ DR
131.) The C++ standard's heading "CJK Unified Ideographs" lists ranges
which also include various presentations forms such as one of the Hebrew
characters previously discussed, but these are genuine ranges of letters
clearly deliberately included; just the heading is wrong.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=9449