This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: Implementing Universal Character Names in identifiers
- From: loewis at informatik dot hu-berlin dot de (Martin v. Löwis)
- To: tromey at redhat dot com
- Cc: Zack Weinberg <zack at codesourcery dot com>, gcc-patches at gcc dot gnu dot org, java at gcc dot gnu dot org
- Date: 01 Nov 2002 10:40:55 +0100
- Subject: Re: Implementing Universal Character Names in identifiers
- References: <200210280715.g9S7FdI2003815@paros.informatik.hu-berlin.de><20021028075111.GB1273@codesourcery.com><j4wuo39c6o.fsf@informatik.hu-berlin.de><20021028183910.GC24090@codesourcery.com><8765vi1inl.fsf@fleche.redhat.com>
Tom Tromey <tromey@redhat.com> writes:
> One is how non-ascii characters are mangled in symbol names. We have
> something in place now, but I don't think we have a strong requirement
> for a particular approach. If something else is preferred for C++, I
> imagine we could change gcj for compatibility. Note that we don't yet
> make ABI stability promises about gcj's output.
That sounds good. Are you currently making use of non-ASCII
identifiers anywhere? If not, would it be acceptable to not provide
them on platforms that lack assembler capabilities?
My plan would be to use UTF-8 in object files everywhere *unless* the
system vendor defines a different mapping (for C99). To my knowledge,
this escape clause would apply on no system at the moment.
[generating C++ header files]
> I assume this is solved by emitting \u escapes in the .h file.
Correct, that should work fine.
Regards,
Martin