This is the mail archive of the libc-alpha@sources.redhat.com mailing list for the glibc 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: iconv_open behaviour on EILSEQ

From: Stefan Hoffmeister <bug dot glibc-gnu dot org at econos dot de>
To: libc-alpha at sources dot redhat dot com
Date: Sat, 04 May 2002 23:42:59 +0200
Subject: Re: iconv_open behaviour on EILSEQ
Organization: Econos
References: <hq58ducfaii8opja2aehdrnrflpg2uucff@4ax.com> <jer8kr3ejd.fsf@sykes.suse.de>

: On Sat, 04 May 2002 21:21:10 +0200, Andreas Schwab wrote:

[quotes from POSIX 1003.1 snipped]

>This is pretty unambiguous, IMHO.  

I see your point.

I'd prefer some more explicit wording along the lines of "even if an
invalid byte sequence ... are the state variables updated." because in
an error case any callee-modified data typically is in an undefined
state.

References:
- iconv_open behaviour on EILSEQ
  - From: Stefan Hoffmeister
- Re: iconv_open behaviour on EILSEQ
  - From: Andreas Schwab

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