From: "M. Warner Losh" <imp@bsdimp.com>
To: qemu-devel@nongnu.org, mle+tools@mega-nerd.com
Subject: Re: [Qemu-devel] [6023] Use a hex value instead of possibly ambiguous 8 bit character
Date: Sun, 14 Dec 2008 09:10:43 -0700 (MST) [thread overview]
Message-ID: <20081214.091043.-399282895.imp@bsdimp.com> (raw)
In-Reply-To: <20081214224559.c54b844a.mle+tools@mega-nerd.com>
In message: <20081214224559.c54b844a.mle+tools@mega-nerd.com>
Erik de Castro Lopo <mle+tools@mega-nerd.com> writes:
: 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.
isprint() also was in many K&R compilers, but that was system
dependent. The VAX I used in college in 1985 had it, as did the 'C'
compiler for my DEC Rainbow and the TOPS-20 C compiler written at my
university...
Warner
next prev parent reply other threads:[~2008-12-14 17:13 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 [this message]
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=20081214.091043.-399282895.imp@bsdimp.com \
--to=imp@bsdimp.com \
--cc=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.