This is the mail archive of the
mailing list for the GCC project.
Re: UTF-8 quotation marks in diagnostics
- From: Martin Sebor <msebor at gmail dot com>
- To: Joseph Myers <joseph at codesourcery dot com>
- Cc: "D. Hugh Redelmeier" <hugh at mimosa dot com>, gcc at gcc dot gnu dot org
- Date: Thu, 22 Oct 2015 17:43:25 -0600
- Subject: Re: UTF-8 quotation marks in diagnostics
- Authentication-results: sourceware.org; auth=none
- References: <alpine dot LRH dot 2 dot 02 dot 1510211705080 dot 3681 at redclaw dot mimosa dot com> <56283B7D dot 9020903 at gmail dot com> <alpine dot DEB dot 2 dot 10 dot 1510221629450 dot 8870 at digraph dot polyomino dot org dot uk> <5629334C dot 7020009 at gmail dot com> <alpine dot DEB dot 2 dot 10 dot 1510221935230 dot 23141 at digraph dot polyomino dot org dot uk>
Again, LC_CTYPE does *not* affect source file interpretation.
I understand what you're saying. What I am saying is that if this
is how c99 behaves it's in conflict with POSIX because LC_CTYPE
is exactly how source file interpretation is specified to be
Determine the locale for the interpretation of sequences of
bytes of text data as characters (for example, single-byte
as opposed to multi-byte characters in arguments and input
I think we should clearly update the documentation to reflect reality
regarding source file encoding, and leave it strictly for wrappers such as
"c99" to specify -finput-charset= options rather than leaving open the
possibility that GCC's own default might change in future.
That sounds reasonable.