From: "AtomicKobold Design" <atomickobold@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: Tue, 24 Oct 2006 10:32:40 -0400 [thread overview]
Message-ID: <c18934c50610240732w164e7048h1e2ff8d2f96f8ac@mail.gmail.com> (raw)
In-Reply-To: <52af7b0e92c11760a5b9d627fd71aa09@plan9.bell-labs.com>
[-- Attachment #1: Type: text/plain, Size: 1036 bytes --]
On 10/20/06, geoff@plan9.bell-labs.com <geoff@plan9.bell-labs.com> wrote:
>
> I think that one of the best arguments for organising header files as
> Plan 9 does is the mess that /usr/include has become on (l)unix. It's
> almost 20MB on Suse 9.1.
>
> Here's an interesting exercise for people who don't see a problem with
> how (l)unix organises /usr/include:
>
> Ask someone (ideally a manager, the higher the rank, the better) to
> find out where under /usr/include on Linux the type time_t is defined
> and the signal SIGINT is declared without using grep or any
> equivalent; they should trace through the include files visually. If
> they return with the correct answers and aren't disgusted with the
> mess under /usr/include, slap some pointy hair on them.
>
>
Yes I agree, they are even larger under S.L.E.D. 10, I believe like 35 MB,
or some such.
IMHO organizing header files.
As far as the above "exercise" no way w/o grep would I in a million years
wanna go through
/usr/include in a *nix system.
[-- Attachment #2: Type: text/html, Size: 1528 bytes --]
next prev parent reply other threads:[~2006-10-24 14:32 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 [this message]
2006-10-23 12:39 ` Rogelio Serrano
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=c18934c50610240732w164e7048h1e2ff8d2f96f8ac@mail.gmail.com \
--to=atomickobold@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).