This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug libc/20687] Non-conformant error description in errlist.c
- From: "carlos at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sourceware dot org
- Date: Wed, 12 Oct 2016 07:13:01 +0000
- Subject: [Bug libc/20687] Non-conformant error description in errlist.c
- Auto-submitted: auto-generated
- References: <bug-20687-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=20687
Carlos O'Donell <carlos at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|WAITING |RESOLVED
Resolution|--- |INVALID
--- Comment #3 from Carlos O'Donell <carlos at redhat dot com> ---
(In reply to Dmitry V. Levin from comment #2)
> This wording was chosen on purpose. GNU Coding Standards (see e.g.
> https://www.gnu.org/prep/standards/html_node/GNU-Manuals.html) say:
> "Please do not use the term “illegal” to refer to erroneous input to a
> computer program. Please use “invalid” for this, and reserve the term
> “illegal” for activities prohibited by law."
Thanks Dmitry. I agree, and in this case I'm going to close this as
RESOLVED/INVALID. There is no rationale I see in POSIX that requires any
specific text, and the GNU Coding Standards clarify why we chose the text we
did.
--
You are receiving this mail because:
You are on the CC list for the bug.