From: Daniel Jacobowitz <drow@false.org>
To: Andreas Schwab <schwab@suse.de>
Cc: Eli Zaretskii <eliz@gnu.org>,
mark.kettenis@xs4all.nl, sje@cup.hp.com,
gdb-patches@sourceware.org
Subject: Re: Patch for isdigit/isalpha/etc. macro arguments
Date: Sun, 08 Apr 2007 14:11:00 -0000 [thread overview]
Message-ID: <20070408141051.GA13486@caradoc.them.org> (raw)
In-Reply-To: <jebqhzcitp.fsf@sykes.suse.de>
On Sun, Apr 08, 2007 at 11:32:34AM +0200, Andreas Schwab wrote:
> Eli Zaretskii <eliz@gnu.org> writes:
>
> >> From: Andreas Schwab <schwab@suse.de>
> >> Cc: mark.kettenis@xs4all.nl, sje@cup.hp.com,
> >> gdb-patches@sourceware.org
> >> Date: Sat, 07 Apr 2007 19:55:08 +0200
> >>
> >> How can it distinguish EOF from '\377'?
> >
> > The same way you want the calling code to do that.
>
> So tell me how to distinguish two identical values?
I don't think we're getting anywhere...
The only thing I can see is that if the caller knows it is not EOF, it
should cast to unsigned char. Otherwise if there are signed
characters on a platform I don't see any way the library can do the
right thing; the cast to int will leave '\377' == EOF.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2007-04-08 14:11 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-06 22:34 Steve Ellcey
2007-04-06 23:06 ` Mark Kettenis
2007-04-06 23:17 ` Steve Ellcey
2007-04-06 23:36 ` Steve Ellcey
2007-04-06 23:51 ` Mark Kettenis
2007-04-06 23:59 ` Steve Ellcey
2007-04-07 6:18 ` Andreas Schwab
2007-04-07 9:16 ` Eli Zaretskii
2007-04-07 9:26 ` Andreas Schwab
2007-04-07 17:32 ` Eli Zaretskii
2007-04-07 17:55 ` Andreas Schwab
2007-04-08 8:00 ` Eli Zaretskii
2007-04-08 9:32 ` Andreas Schwab
2007-04-08 14:11 ` Daniel Jacobowitz [this message]
2007-04-10 21:16 ` Steve Ellcey
2007-04-10 21:21 ` Daniel Jacobowitz
2007-04-10 21:52 ` DJ Delorie
2007-04-11 3:36 ` Eli Zaretskii
2007-04-09 12:57 ` DJ Delorie
2007-04-09 13:20 ` Andreas Schwab
2007-04-09 13:43 ` DJ Delorie
2007-04-09 14:17 ` Andreas Schwab
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=20070408141051.GA13486@caradoc.them.org \
--to=drow@false.org \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=mark.kettenis@xs4all.nl \
--cc=schwab@suse.de \
--cc=sje@cup.hp.com \
/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