This is the mail archive of the gcc@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]

Re: revised proposal for GCC and non-Ascii source files


> OK, suppose we translate `\u00C0' to `..u00c0' instead?

That would work, at the first glance.

> If that doesn't work, perhaps you can suggest an escape sequence
> does work,

This is exactly the problem: I could not come up with a good solution;
all 'funny' characters are already taken.

> 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.

C++ tries '$', then '.', then '_'. Because the latter may give
conflicts, we put __static_ in front of the entire identifier
(i.e. __static_1F_u00C0).

Regards,
Martin


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