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: NO_DOLLAR_IN_LABEL


> I have proposed such an encoding.  See gcc/cp/gxxint.texi.
> (That is not to say that I will make any claims that that is
> particularly good encoding.)

For C++ and Java, it is perfect. It fails for C. Consider

extern "C" void x\u00c6(void);

Using your encoding, we get 'x_u00C6U' (or perhaps 'U6x_00C6',
depending on the interpretation). Both are valid, non-reserved
identifiers on their own.

I find it desirable to support C linkage to such names for C++, with
no hidden restrictions or potential clashes.

> But "major platforms" is not the issue.  Most or all major platforms
> support gas.

Even for gas, we have the problem of non-Unicode non-ASCII
identifiers. Under Paul's proposal, we have to support these unless
a) A conversion to Unicode is available in the C library and
b) the user gave the -funify-names option or

Regards,
Martin


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