qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Erik de Castro Lopo <mle+tools@mega-nerd.com>
To: 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 22:45:59 +1100	[thread overview]
Message-ID: <20081214224559.c54b844a.mle+tools@mega-nerd.com> (raw)
In-Reply-To: <alpine.DEB.1.00.0812141217390.2014@eeepc-johanness>

Johannes Schindelin wrote:

> 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 know, there are many people on this list who are all too happy to rely 
> on new-fangled C99 stuff or lock themselves (and others) in with GCCisms. 
> Peronally, though, I find it utterly stupid to do that unless you really 
> have to.

isprint is part of C89 and any compiler less than 20 years old should
support it.

Erik
-- 
-----------------------------------------------------------------
Erik de Castro Lopo
-----------------------------------------------------------------
Complex problems have simple easy to understand wrong answers.

  reply	other threads:[~2008-12-14 11:46 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 [this message]
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
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=20081214224559.c54b844a.mle+tools@mega-nerd.com \
    --to=mle+tools@mega-nerd.com \
    --cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).