From: Stan Shebs <shebs@apple.com>
To: Neil Booth <neil@daikokuya.demon.co.uk>
Cc: Phil Edwards <pedwards@disaster.jaj.com>,
Bryce McKinlay <bryce@waitaki.otago.ac.nz>,
gcc@gcc.gnu.org
Subject: Re: Darwin vs. libstdc++
Date: Tue, 09 Oct 2001 11:29:00 -0000 [thread overview]
Message-ID: <3BC341A1.3C1EC15@apple.com> (raw)
In-Reply-To: <20011009191753.A4712@daikokuya.demon.co.uk>
Neil Booth wrote:
>
> Stan Shebs wrote:-
>
> > Really? I don't see anything in my C89 or C99 specs that suggests
> > that isalnum and friends don't need function definitions. For one
> > thing, you can't take the address of a macro, so the standard would
> > have to say explicitly that the address of isalnum is undefined.
>
> You could have both. Anything with a following '(' uses the macro.
> Taking the address of the function will not have a following '(', and
> so would not be treated by CPP as a macro invocation.
Exactly, which is why I suspect that people think the standard
doesn't require that functions be available. One of those reasons
to have testsuite, so that well-meaning people don't remove the
required bits and leave only the optimization in the headers.
(Ironically, this is correct in every other flavor of BSD that I
looked at - only NeXT/Apple managed to get this wrong, haven't
studied the version trail to find an actual miscreant though.)
Stan
next prev parent reply other threads:[~2001-10-09 11:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-08 23:50 Bryce McKinlay
2001-10-09 6:19 ` Stan Shebs
2001-10-09 23:58 ` Bryce McKinlay
2001-10-09 10:30 ` Phil Edwards
2001-10-09 11:01 ` Stan Shebs
2001-10-09 11:18 ` Neil Booth
2001-10-09 11:29 ` Stan Shebs [this message]
2001-10-09 11:59 ` Dale Johannesen
2001-10-09 13:13 ` Geoff Keating
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=3BC341A1.3C1EC15@apple.com \
--to=shebs@apple.com \
--cc=bryce@waitaki.otago.ac.nz \
--cc=gcc@gcc.gnu.org \
--cc=neil@daikokuya.demon.co.uk \
--cc=pedwards@disaster.jaj.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).