This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [PATCH] Revised: utf-16 and utf-32 support in C and C++

From: Jason Merrill <jason at redhat dot com>
To: Kris Van Hees <kris dot van dot hees at oracle dot com>
Cc: gcc-patches at gcc dot gnu dot org
Date: Wed, 26 Mar 2008 14:21:32 -0400
Subject: Re: [PATCH] Revised: utf-16 and utf-32 support in C and C++
References: <20080325124715.GJ19427@oracle.com> <20080325195700.GK19427@oracle.com>

Incidentally, in your initial patch you wrote:

The aforementioned proposals do not specifically state what should be
done when a UTF-16 (char16_t) character literal contains a 32-bit
universal character (\Unnnnnnnn).  This implementation will issue an
error about the constant being too long.

But in the latest C++ working draft I see

                                                                        If the
  value is not representable within 16 bits, the program is ill-formed.

Which seems to specify the behavior you mention.

Jason

References:
- [PATCH] Revised: utf-16 and utf-32 support in C and C++
  - From: Kris Van Hees
- Re: [PATCH] Revised: utf-16 and utf-32 support in C and C++
  - From: Kris Van Hees

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]