Email List: Xaustin-group-lX
[All Lists]

Re: multibyte C locale

To: austin-group-l@xxxxxxxxxxxxx
Subject: Re: multibyte C locale
From: Geoff Clare <gwc@xxxxxxxxxxxxx>
Date: Mon, 2 Nov 2009 11:00:41 +0000
References: <20091030181139.GI28296@xxxxxx> <8CC27A9B7A337AB-1BD0-9799@webmail-d053.sysops.aol.com> <OF061B1E55.0E7681F0-ON8525765F.006B7217-8525765F.006BDF48@xxxxxx> <8CC27B486F71509-1BD0-AA5A@webmail-d053.sysops.aol.com> <4AEB8AC6.2010002@xxxxxx> <200910310414.n9V4ENxJ024489@xxxxxx> <4AEBC24A.8020705@xxxxxx>
Eric Blake <ebb9@xxxxxx> wrote, on 30 Oct 2009:
> 
> The fact
> that the file contains bytes that do not correspond to the portable
> character set required of the POSIX locale means that this is no longer a
> compliant environment

It doesn't make any sense for the contents of input files to be a
factor in whether or not an application is running in a conforming
environment.

In the particular case of character encodings, the standard
requires interfaces such as mbtowc() to fail with EILSEQ if
an invalid character sequence is detected.  It could not make
such a requirement if the presence of an invalid character
sequence in the input meant that the function was being called
in a non-conforming environment.

-- 
Geoff Clare <g.clare@xxxxxx>
The Open Group, Thames Tower, Station Road, Reading, RG1 1LX, England

<Prev in Thread] Current Thread [Next in Thread>