From: John Carr <jfc@mit.edu>
To: "Kaveh R. Ghazi" <ghazi@caip.rutgers.edu>
Cc: egcs@cygnus.com
Subject: Re: system.h
Date: Mon, 16 Feb 1998 13:10:00 -0000 [thread overview]
Message-ID: <199802162046.PAA23337@contents-vnder-pressvre.MIT.EDU> (raw)
In-Reply-To: <199802161933.OAA03190@caip.rutgers.edu>
> > Here is an example: on x86 SVR4 systems <sys/stat.h> defines several
> > static functions.
>
> does it potentially increase the size of cc1 by 0.001%, 1%, 5%?
About 1-2% in this case.
> Maybe a good compromise is to split it into two files,
> system.h and system2.h.
That's better than testing a macro. I suggest different calling the
files ansi.h and system.h (corresponding, more or less, to ANSI and
POSIX interfaces).
next prev parent reply other threads:[~1998-02-16 13:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-02-16 16:56 system.h Kaveh R. Ghazi
1998-02-16 13:10 ` John Carr [this message]
1998-02-17 23:59 ` system.h Jeffrey A Law
-- strict thread matches above, loose matches on Subject: below --
1998-02-17 10:40 system.h Kaveh R. Ghazi
1998-02-15 18:47 system.h Kaveh R. Ghazi
1998-02-16 5:16 ` system.h John Carr
1998-02-14 3:29 system.h John Carr
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=199802162046.PAA23337@contents-vnder-pressvre.MIT.EDU \
--to=jfc@mit.edu \
--cc=egcs@cygnus.com \
--cc=ghazi@caip.rutgers.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 read-only IMAP folder(s) and NNTP newsgroup(s).