From: Gerald Pfeifer <gerald@pfeifer.com>
To: Joern Rennecke <amylaar@spamcop.net>
Cc: "Paulo J. Matos" <pocmatos@gmail.com>, gcc@gcc.gnu.org
Subject: Re: C99 Status - inttypes.h
Date: Sun, 21 Aug 2011 19:27:00 -0000 [thread overview]
Message-ID: <alpine.LNX.2.00.1108212125530.2761@gerinyyl.fvgr> (raw)
In-Reply-To: <20110722112215.utk9zqjq0c0wss0o-nzlynne@webmail.spamcop.net>
On Fri, 22 Jul 2011, Joern Rennecke wrote:
>>>> But readers will focus on the word "Issue" here and think that there is
>>>> something missing. Perhaps there should be a footnote explaining that
>>>> glibc/eglibc has the needed support, but that other libraries might not.
>>> I agree. It should say something as "Library Dependent", and report
>>> glibc status.
> It still makes sense to clarify the language to indicate that, depending on
> the library used, this might be, in fact, a library non-issue.
> [...]
> I agree that trying to track every library there would be a maintenance
> burden, but giving one example of a library that works is meaningful.
> And, since GCC is still a GNU project, mentioning the status of GNU libc
> doesn't seem that arbitrary.
Can you propose a change along these lines? I think it does make
sense, both to be more clear on what may be a (non-)issue and to
refer to GNU libc as a reference implementation where that makes
sense.
Gerald
next prev parent reply other threads:[~2011-08-21 19:27 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-21 14:30 Diogo Sousa
2011-07-21 15:52 ` Joseph S. Myers
2011-07-21 18:13 ` Joe Buck
2011-07-22 11:05 ` Diogo Sousa
2011-07-22 13:03 ` Paulo J. Matos
2011-07-22 15:38 ` Joern Rennecke
2011-07-22 17:43 ` Paulo J. Matos
2011-07-22 20:12 ` James Dennett
2011-07-23 19:29 ` Weddington, Eric
2011-07-23 21:10 ` Eric Botcazou
2011-07-23 22:47 ` Weddington, Eric
2011-08-21 19:27 ` Gerald Pfeifer [this message]
2011-09-25 13:00 ` Joern Rennecke
2011-09-25 22:49 ` Joseph S. Myers
2011-09-25 22:53 ` Gerald Pfeifer
2011-09-26 7:11 ` Joseph S. Myers
2011-07-21 16:06 ` Basile Starynkevitch
2011-07-21 22:45 ` Ian Lance Taylor
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=alpine.LNX.2.00.1108212125530.2761@gerinyyl.fvgr \
--to=gerald@pfeifer.com \
--cc=amylaar@spamcop.net \
--cc=gcc@gcc.gnu.org \
--cc=pocmatos@gmail.com \
/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).