From: "Rogelio Serrano" <rogelio.serrano@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] Include guards and multiple includes
Date: Mon, 23 Oct 2006 20:39:10 +0800 [thread overview]
Message-ID: <a9951d2a0610230539o59e57e30vbd05a5676ab81e17@mail.gmail.com> (raw)
In-Reply-To: <219D85AA-959D-464C-90C2-0F132809F0B9@telus.net>
On 10/21/06, Paul Lalonde <plalonde@telus.net> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> I'm trying to convince some non-believers that include files should
> not include other include files, and that instead they should state
> their dependencies; they want hard data before they commit to such a
> scheme.
>
> Is there some study kicking around that I could point them at rather
> than re-factor our code base and time the resulting builds? I know
> the plan9 headers largely follow this pattern.
>
> Paul
I think this has more to do with minimising the preprocessor logic. I
like the plan 9 include tree more than the traditional unix include
mess. In my programs I dont use macros anywhere. none. nada. zero.
If one could only get rid of the preprocessor...
--
the thing i like with my linux pc is that i can sum up my complaints in 5 items
next prev parent reply other threads:[~2006-10-23 12:39 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-20 18:45 Paul Lalonde
2006-10-20 19:27 ` Joel Salomon
2006-10-20 20:18 ` Russ Cox
2006-10-20 20:37 ` Paul Lalonde
2006-10-22 16:37 ` Joel Salomon
2006-10-23 12:29 ` Charles Forsyth
2006-10-20 23:15 ` geoff
2006-10-20 23:39 ` Bruce Ellis
2006-10-24 14:32 ` AtomicKobold Design
2006-10-23 12:39 ` Rogelio Serrano [this message]
2006-10-23 12:41 ` erik quanstrom
2006-10-23 12:52 ` Rogelio Serrano
2006-10-23 13:26 ` erik quanstrom
2006-10-23 15:30 ` Joel Salomon
2006-10-23 18:43 ` Charles Forsyth
2006-10-23 19:12 ` Joel Salomon
2006-10-23 20:23 ` geoff
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=a9951d2a0610230539o59e57e30vbd05a5676ab81e17@mail.gmail.com \
--to=rogelio.serrano@gmail.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).