From: "Blue Swirl" <blauwirbel@gmail.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Andreas Schwab <schwab@suse.de>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [6023] Use a hex value instead of possibly ambiguous 8 bit character
Date: Sun, 14 Dec 2008 14:15:41 +0200 [thread overview]
Message-ID: <f43fc5580812140415t1039e4f1vfdcbd4b570e8553d@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.1.00.0812141217390.2014@eeepc-johanness>
On 12/14/08, Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:
> Hi,
>
>
> Please Cc: me, I only did not miss your message because it is a slow
> Sunday morning (_and_ I am not in a deep hacking session).
>
>
>
>
> On Sun, 14 Dec 2008, Andreas Schwab wrote:
>
> > Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
> >
> > > +#define ADD_CHAR(c) buffer[j++] = (c) ? '.' : (c)
>
>
> Oops. This is obviously wrong, and should read
>
>
> #define ADD_CHAR(c) buffer[j++] = (c) < ' ' ? '.' : (c)
>
> > isprint(c) perhaps?
>
>
> I vote against using isprint(c). The code is simple as it is, otherwise
> you'd have to look up what isprint() does, _and_ rely on isprint() being
> present.
I agree that we should not use plain old isprint, but instead the
highly advanced, omnipresent qemu_isprint which has none of the
problems of what isprint may have. ;-)
next prev parent reply other threads:[~2008-12-14 12:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-14 9:30 [Qemu-devel] [6023] Use a hex value instead of possibly ambiguous 8 bit character Blue Swirl
2008-12-14 10:34 ` Johannes Schindelin
2008-12-14 10:41 ` Blue Swirl
2008-12-14 10:54 ` Johannes Schindelin
2008-12-14 11:11 ` Andreas Schwab
2008-12-14 11:23 ` Johannes Schindelin
2008-12-14 11:45 ` Erik de Castro Lopo
2008-12-14 12:00 ` Johannes Schindelin
2008-12-14 17:16 ` Jamie Lokier
2008-12-14 16:10 ` M. Warner Losh
2008-12-14 12:15 ` Blue Swirl [this message]
2008-12-14 12:09 ` Blue Swirl
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=f43fc5580812140415t1039e4f1vfdcbd4b570e8553d@mail.gmail.com \
--to=blauwirbel@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=qemu-devel@nongnu.org \
--cc=schwab@suse.de \
/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 NNTP newsgroup(s).