------- Additional Comments From jsm at polyomino dot org dot uk 2004-10-20 17:59 ------- Subject: Re: HAVE_LANGINFO_CODESET never defined
On Wed, 20 Oct 2004, mckinlay at redhat dot com wrote: > Do we really want to fix this? > > The "buggy" behaviour actually seems better here because it more closely matches > what other Java compilers do and seems to have resulted in less complaints from > users since it "broke". > > I propose we close this as WONTFIX and update the documentation to specify that > Utf8 is the default encoding for input files unless specified otherwise with the > --encoding flag. Comments? I don't know what is best for Java, but for the C compiler POSIX specifies use of locale to determine the encoding of source files. In addition, if HAVE_LANGINFO_CODESET were set properly then people using UTF-8 locales would get proper quotes in error messages. If particular languages do not want this or don't work with it at present, they need not use the locale for source files, but the configure test should go in for the use of diagnostics if nothing else. I understand Zack has proposals for changes to cpplib which would mean that for well-behaved locale character sets (supersets of ASCII, roughly) stray invalid characters in comments can be ignored rather than causing an error through not being in the locale character set (and speed up cpplib by not needing to pass most of most files through iconv). -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=15575
