From: anothy@cosym.net
To: 9fans@cse.psu.edu
Subject: Re: [9fans] /ape/sys/time.h
Date: Wed, 19 Sep 2001 11:23:34 -0400 [thread overview]
Message-ID: <20010919152346.456A319A4E@mail.cse.psu.edu> (raw)
to expand on rog's response:
there are a number of header files which arn't defined in pure
ANSI or POSIX which many vendors include in "ANSI/POSIX"
environments anyway. Plan 9's APE takes a stricter approach;
if you say you're using ANSI/POSIX, that's what you get. if you
want more, you need to #define for those headers. APE
ensures you get this right by including lines that're not valid
C code, so the compiler fails, making sure you'll notice your
mistake. the common fix is to add the defines to your
command line or ma?ke?file.
check out the APE paper (/sys/doc/ape.ps), page 3, for a list
of what defines are understood to allow extra stuff. as rog
noted, _BSD_EXTENSION is the most common.
-α.
next reply other threads:[~2001-09-19 15:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-19 15:23 anothy [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-09-19 11:24 rog
2001-09-19 7:33 pac
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=20010919152346.456A319A4E@mail.cse.psu.edu \
--to=anothy@cosym.net \
--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).