This is the mail archive of the 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] PR18785: Support non-native execution charsets (Kai Henningsen) writes:

>>       - All characters within the basic source character set must have
>>         the same code points that they do in ...
>>    * The host character set: that is, the narrow execution character
>>      set of the host machine.  At present this is always either ASCII
>>      or EBCDIC, and we assume that whichever variant of EBCDIC is in
>>      use does not alter the code points corresponding to the basic
>>      source character set.
> You do realize, I hope, that not all EBCDIC codepages have consistent  
> codepoints for at least {}[] (probably more)? This makes that "must have  
> the same code points" thing rather hard.

I'm aware.  (There's a whole bunch more.)  However, as long as the
people actually using GCC hosted on IBM mainframes are okay with
having to use a host compiler consistent with safe-ctype.h and
whichever UAX specifies UTF-EBCDIC, it's not a problem in practice.

> I still believe that rule is utterly misguided. Trying to use
> UTF-EBCDIC really is ALWAYS a mistake.

Show me a viable alternative.  "Viable" includes "does not force me to
replace every last character constant in cpplib with a magic number"
and "does not force all the aforementioned people using GCC hosted on
EBCDIC systems to run all their source code through iconv twice per


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