From: James Dennett <james.dennett@gmail.com>
To: "Paulo J. Matos" <pocmatos@gmail.com>
Cc: gcc@gcc.gnu.org
Subject: Re: C99 Status - inttypes.h
Date: Fri, 22 Jul 2011 20:12:00 -0000 [thread overview]
Message-ID: <CAKNGpgq6SSyd2AEMtYgEEdov_SfWR_2JQ+YGivkwHwRk9H0-6w@mail.gmail.com> (raw)
In-Reply-To: <j0c5fl$sm6$1@dough.gmane.org>
On Fri, Jul 22, 2011 at 8:37 AM, Paulo J. Matos <pocmatos@gmail.com> wrote:
> On 22/07/11 16:22, Joern Rennecke wrote:
>>>
>>> I have to disagree, library issue means that it's an issue with the
>>> library, not gcc.
>>
>> 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.
>>
>
> We might be interpreting this differently. When I you it's a "library
> issue", I understand it as begin something that has to do with the library,
> not that it is a definite problem with the library. Therefore if I want to
> see what's the feature status I should check the library documentation. I
> didn't think that saying it is a library issue would mean that it is
> definitely broken/missing in the library.
>
> Then again my native language is not english. However, by raising this
> you're proving your point. If we can avoid different interpretations then
> better.
While your use of the term "a library issue" meaning roughly "the
responsibility of the library" is entirely correct, unfortunately the
term "issue" has been hijacked of late as a euphemism for "problem",
which leaves us without a good, unambiguous way to refer to issues
that may not, in fact, be problems.
-- James
next prev parent reply other threads:[~2011-07-22 18:41 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 [this message]
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
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=CAKNGpgq6SSyd2AEMtYgEEdov_SfWR_2JQ+YGivkwHwRk9H0-6w@mail.gmail.com \
--to=james.dennett@gmail.com \
--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).