Re: UTF-8, UTF-16 and UTF-32

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hello Eljay & Andrew

What you are proposing is not C, and is not C++.  FSF does not control ISO
9899 nor ISO 14882.  GCC does not drive platform ABI.

The heart of this issue is that GCC is not compatible with MS VC++, by defining wchar_t as 4-bytes and not providing any 16-bit Unicode support - it just going to be too hard to continue porting to Linux.

At the end of the day if you want to live in a world where you only consider yourself - then you can live in that world by yourself. Like you said, if I don't like it I can use another language and GCC will become irrelevant, you can all go your own separate way.

Also I have written my own scripting language, designed to add functionality post installation, its not that hard.

Sure, but you so far have failed to convince anyone that a bad decision
has been made.

I wont bother repeating myself, it not my responsibility to cure your dogma, it just the end of me using GCC. I am sure that many other developers will run into the same problem and choose the same solution.


It was fun,
Dallas.
http://www.ekkySoftware.com/


[Index of Archives]     [Linux C Programming]     [Linux Kernel]     [eCos]     [Fedora Development]     [Fedora Announce]     [Autoconf]     [The DWARVES Debugging Tools]     [Yosemite Campsites]     [Yosemite News]     [Linux GCC]

  Powered by Linux