From: Daniel Jacobowitz <drow@false.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [patch] printf "%p" gdb internal error fix
Date: Sat, 15 Sep 2007 18:40:00 -0000 [thread overview]
Message-ID: <20070915184002.GA31306@caradoc.them.org> (raw)
In-Reply-To: <uabrnkdbv.fsf@gnu.org>
On Sat, Sep 15, 2007 at 09:12:20PM +0300, Eli Zaretskii wrote:
> We can, if we have the exact title and other details.
All I know is:
http://www.open-std.org/jtc1/sc22/wg14/www/standards
Sorry.
> > Can't we describe it as a mostly complete C89 printf instead of a
> > mostly incomplete C99 printf?
>
> I don't think it's right to ask our readers to be familiar with the
> history of the C standards. That is why I didn't even mention C99 (or
> any other standard).
I don't think it's right to have it both ways. If we say it behaves
like the C "printf" function - which I personally think is the most
useful way to describe it, for readers' benefit - then it behooves us
to say which one. There are probably a dozen or more variations. I
can name five off the top of my head: C89, C99, SUSv2, Microsoft VC++
(%I64), C++ (which has wchar_t but not some other C99 features).
I don't feel terribly strongly about this, though, and you're
definitely the expert.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2007-09-15 18:40 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-10 17:20 Jan Kratochvil
2006-09-10 19:31 ` Mark Kettenis
2006-09-10 22:00 ` Daniel Jacobowitz
2007-09-04 14:19 ` Daniel Jacobowitz
2007-09-04 20:43 ` Eli Zaretskii
2007-09-04 20:53 ` Daniel Jacobowitz
2007-09-15 9:00 ` Eli Zaretskii
2007-09-15 13:52 ` Daniel Jacobowitz
2007-09-15 14:55 ` Andreas Schwab
2007-09-15 15:16 ` Eli Zaretskii
2007-09-15 15:18 ` Eli Zaretskii
2007-09-15 16:12 ` Daniel Jacobowitz
2007-09-15 18:12 ` Eli Zaretskii
2007-09-15 18:40 ` Daniel Jacobowitz [this message]
2007-09-15 21:59 ` Eli Zaretskii
2007-09-15 22:17 ` Daniel Jacobowitz
2007-09-15 16:21 ` Joseph S. Myers
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=20070915184002.GA31306@caradoc.them.org \
--to=drow@false.org \
--cc=eliz@gnu.org \
--cc=gdb-patches@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