From: Eli Zaretskii <eliz@gnu.org>
To: gdb-patches@sourceware.org
Subject: Re: [ob] More warnings; Call for assistance
Date: Sat, 21 Jan 2006 10:07:00 -0000 [thread overview]
Message-ID: <u7j8trj1f.fsf@gnu.org> (raw)
In-Reply-To: <20060120230641.GA21181@nevyn.them.org> (message from Daniel Jacobowitz on Fri, 20 Jan 2006 18:06:41 -0500)
> Date: Fri, 20 Jan 2006 18:06:41 -0500
> From: Daniel Jacobowitz <drow@false.org>
>
> > > avoid the use of standard printf
> >
> > Avoid? how? are you saying that we should write our own version of
> > printf?
>
> Certainly we shouldn't write a new one - but the advantage of being a
> GNU project and licensed under the GPL is that there's already at least
> two we can choose from, probably more :-)
Doing so would probably get us also the possible bugs of those
implementations, but that's a minor issue.
A more important issue is how do we convince ourselves that the
implementation we use does not blow up in some cases as well, just in
different ones? `printf' implementations are traditionally reckless
about bad format strings. Are the ones you suggest any better?
next prev parent reply other threads:[~2006-01-21 10:07 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-17 15:17 Daniel Jacobowitz
2006-01-17 15:22 ` Daniel Jacobowitz
2006-01-17 19:37 ` Jim Blandy
2006-01-17 19:46 ` Daniel Jacobowitz
2006-01-17 20:11 ` Eli Zaretskii
2006-01-20 23:06 ` Daniel Jacobowitz
2006-01-21 10:07 ` Eli Zaretskii [this message]
2006-01-21 15:18 ` Daniel Jacobowitz
2006-01-17 20:57 ` Jim Blandy
2006-01-17 20:17 ` Eli Zaretskii
2006-01-20 23:09 ` Daniel Jacobowitz
2006-01-17 20:19 ` Eli Zaretskii
2006-01-17 20:23 ` Daniel Jacobowitz
2006-01-17 21:08 ` Eli Zaretskii
2006-01-17 21:14 ` Daniel Jacobowitz
2006-01-18 4:16 ` Eli Zaretskii
2006-01-18 1:15 ` Jim Blandy
2006-01-18 23:33 ` Daniel Jacobowitz
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=u7j8trj1f.fsf@gnu.org \
--to=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