srintuar26 wrote on 2003-07-03: > Another suggestion for your language: keep the source code in the same > encoding as your strings. If you want a UTF-32 language, then require > all source code to be encoded in that same encoding as well. Allow > identifiers, comments, and literals to all be in that encoding so you > dont get stuck in C++'s situation, where you have to use English for > almost everything. > Why would one want a UTF-32 language? I understand the desire for a Unicode lannguage, whose purpose should be hide the internal implmenetation from the programmer. But then, why would you want the source in anything but UTF-8? OK, you might (or might not) want latin-1, but why UTF-32 ?-). Especially since the OP also wants the language to work on unix, UTF-32 source will be very painful for the programmers...
-- Beni Cherniavsky <[EMAIL PROTECTED]> "Reading the documentation I felt like a kid in a toy shop." -- Phil Thompson on Python's standard library -- Linux-UTF8: i18n of Linux on all levels Archive: http://mail.nl.linux.org/linux-utf8/
