This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: revised proposal for GCC and non-Ascii source files
- To: martin at mira dot isdn dot cs dot tu-berlin dot de
- Subject: Re: revised proposal for GCC and non-Ascii source files
- From: Paul Eggert <eggert at twinsun dot com>
- Date: Tue, 29 Dec 1998 05:51:39 -0800 (PST)
- CC: rms at gnu dot org, zack at rabi dot columbia dot edu, bothner at cygnus dot com, amylaar at cygnus dot co dot uk, gcc2 at gnu dot org, egcs at cygnus dot com
- References: <199812290158.RAA12839@shade.twinsun.com> <199812290934.KAA00209@mira.isdn.cs.tu-berlin.de>
Date: Tue, 29 Dec 1998 10:34:39 +0100
From: Martin von Loewis <martin@mira.isdn.cs.tu-berlin.de>
class F{
static int u00C0;
};
This is mangled as '_1F.u00C0'.... There still is a conflict with
extern "C" void _1F\u00C0();
OK, suppose we translate `\u00C0' to `..u00c0' instead? If we use two
dots, does that avoid collisions with C++ name mangling? If that
doesn't work, perhaps you can suggest an escape sequence does work,
e.g. by using a name that can be reserved by the implementation
(e.g. `.__u00c0').
Date: Tue, 29 Dec 1998 10:37:52 +0100
From: Martin von Loewis <martin@mira.isdn.cs.tu-berlin.de>
What do we do with platforms that have NO_DOT_IN_LABELS?
IMHO, they either lose, or we try $. If they also have
NO_DOLLAR_IN_LABELS, they should definitely lose (i.e. identifiers
with funny characters are rejected).
What does C++ name mangling do on platforms with NO_DOT_IN_LABELS
and/or NO_DOLLAR_IN_LABELS? If C++ name mangling tries `.', then `$',
and then fails, then non-ASCII name mangling should be able to do the
same thing.