From: "Russ Cox" <rsc@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] C99
Date: Tue, 27 Feb 2001 08:19:45 -0500 [thread overview]
Message-ID: <20010227131948.88CC8199F1@mail.cse.psu.edu> (raw)
Is there any plan to update ape/cc to be C99 compliant?
Whoops. I misread this, thinking it said "way" not "plan".
A slightly helpful answer: I printed the spec and got _very_
scared away. In my cynical view, it's not clear how much
good it would do anyway. The even larger can of worms is the
Single Unix spec. I doubt the number of exactly conforming
C99/SUSV programs is much higher than the number of exactly
conforming ANSI/POSIX programs currently in existence.
A few weeks ago, I rewrote u9fs with the Single Unix spec
in hand, so that it would just compile everywhere without
any changes whatsoever. But it was not to be. As usual,
vendors' implementations vary in subtle ways so that we're
still not at "write once, compile & run anywhere" in any
real sense.
Russ
next reply other threads:[~2001-02-27 13:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-27 13:19 Russ Cox [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-10-04 18:34 Joel “chesky” Salomon
2006-10-04 19:24 ` erik quanstrom
2001-02-28 2:51 okamoto
2001-02-27 14:27 forsyth
2001-02-27 14:25 Russ Cox
2001-02-28 9:30 ` Douglas A. Gwyn
2001-02-27 13:18 rob pike
2001-02-27 13:12 Russ Cox
2001-02-27 10:43 David Rubin
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=20010227131948.88CC8199F1@mail.cse.psu.edu \
--to=rsc@plan9.bell-labs.com \
--cc=9fans@cse.psu.edu \
/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).