public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bruno at clisp dot org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug libc/29913] iconv(3) is not POSIX compliant, and does not conform to linux man-pages manual
Date: Sun, 19 Feb 2023 00:40:21 +0000 [thread overview]
Message-ID: <bug-29913-131-ucm7A6BsW3@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29913-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=29913
Bruno Haible <bruno at clisp dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |bruno at clisp dot org
--- Comment #4 from Bruno Haible <bruno at clisp dot org> ---
> i have reported this in the past but the issue was closed.
This was in https://sourceware.org/bugzilla/show_bug.cgi?id=22908 . Please mark
this bug as related to #22908.
> POSIX defined EILSEQ only for
>
> [EILSEQ] Input conversion stopped due to an input byte that does not belong to the input codeset.
This sentence only means that when /input conversion stopped due to an input
byte that does not belong to the input codeset/, the function shall fail with
error EILSEQ. It does *not* forbid the function to fail with error EILSEQ for
other reasons. It also does *not* forbid the function to fail with other error
values for other reasons.
This is not specific to iconv; it holds for all functions specified by POSIX.
See
https://pubs.opengroup.org/onlinepubs/9699919799.2018edition/functions/V2_chap01.html
section 1.2.
> The Linux man-pages 6.01 manual (2022‐10‐09) says the same.
Nope, it does not say so. According to your interpretation, where this man page
says "The conversion can stop for four reasons" you would like to add a 5th
case.
According to my interpretation of the man page (and I wrote that man page
originally), "An invalid multibyte sequence is encountered in the input" may
also - depending on the implementation - include the case of input that cannot
be meaningfully converted, neither in a reversible nor in a nonreversible way.
In summary: Please close this ticket as INVALID.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2023-02-19 0:40 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-16 23:03 [Bug libc/29913] New: " steffen at sdaoden dot eu
2023-02-18 20:48 ` [Bug libc/29913] " rrt at sc3d dot org
2023-02-18 21:20 ` rrt at sc3d dot org
2023-02-18 22:43 ` steffen at sdaoden dot eu
2023-02-19 0:40 ` bruno at clisp dot org [this message]
2023-02-19 0:51 ` bruno at clisp dot org
2023-02-19 1:58 ` steffen at sdaoden dot eu
2023-02-19 10:06 ` rrt at sc3d dot org
2023-02-19 10:15 ` rrt at sc3d dot org
2023-02-19 10:22 ` rrt at sc3d dot org
2023-02-19 22:57 ` steffen at sdaoden dot eu
2023-02-19 23:02 ` steffen at sdaoden dot eu
2023-02-20 20:09 ` steffen at sdaoden dot eu
2023-02-20 20:54 ` steffen at sdaoden dot eu
2023-02-20 21:52 ` steffen at sdaoden dot eu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-29913-131-ucm7A6BsW3@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).