This is the mail archive of the gcc@gcc.gnu.org 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: --enable-c-mbchar weirdness

From: Phil Edwards <phil at jaj dot com>
To: Zack Weinberg <zack at codesourcery dot com>
Cc: Arkadiusz Miskiewicz <misiek at pld dot ORG dot PL>, gcc at gcc dot gnu dot org
Date: Tue, 27 Aug 2002 13:38:12 -0400
Subject: Re: --enable-c-mbchar weirdness
References: <87u1lgpeqv.fsf@arm.t19.ds.pwr.wroc.pl> <20020827162345.GE31786@codesourcery.com>

On Tue, Aug 27, 2002 at 09:23:45AM -0700, Zack Weinberg wrote:
> On Tue, Aug 27, 2002 at 04:18:00PM +0200, Arkadiusz Miskiewicz wrote:
> > Is this how --enable-c-mbchar is supposed to work? Different
> > result of compilation depending on used locale? Strange...
> 
> Yes, unfortunately, we do not yet have a way for source files to
> indicate their encoding.  Also, --enable-c-mbchar has gone unused for
> a long time and is therefore likely to have bugs.

As an aside, both gcc and libstdc++-v3 pay attention to this option.  (Not
that this effects the OP's question, just FYI.)


Phil

-- 
I would therefore like to posit that computing's central challenge, viz. "How
not to make a mess of it," has /not/ been met.
                                                 - Edsger Dijkstra, 1930-2002

References:
- --enable-c-mbchar weirdness
  - From: Arkadiusz Miskiewicz
- Re: --enable-c-mbchar weirdness
  - From: Zack Weinberg

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