[prev in list] [next in list] [prev in thread] [next in thread] 

List:       9fans
Subject:    Re: [9fans] Include guards and multiple includes
From:       "AtomicKobold Design" <atomickobold () gmail ! com>
Date:       2006-10-24 14:32:40
Message-ID: c18934c50610240732w164e7048h1e2ff8d2f96f8ac () mail ! gmail ! com
[Download RAW message or body]

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 #3 (text/html)]

<br><br><div><span class="gmail_quote">On 10/20/06, <b class="gmail_sendername"><a \
href="mailto:geoff@plan9.bell-labs.com">geoff@plan9.bell-labs.com</a></b> &lt;<a \
href="mailto:geoff@plan9.bell-labs.com">geoff@plan9.bell-labs.com </a>&gt; \
wrote:</span><blockquote class="gmail_quote" style="margin-top: 0; margin-right: 0; \
margin-bottom: 0; margin-left: 0; margin-left: 0.80ex; border-left-color: #cccccc; \
border-left-width: 1px; border-left-style: solid; padding-left: 1ex"> I think that \
one of the best arguments for organising header files as<br>Plan 9 does is the mess \
that /usr/include has become on (l)unix.&nbsp;&nbsp;It's<br>almost 20MB on Suse \
9.1.<br><br>Here's an interesting exercise for people who don't see a problem with \
<br>how (l)unix organises /usr/include:<br><br>Ask someone (ideally a manager, the \
higher the rank, the better) to<br>find out where under /usr/include on Linux the \
type time_t is defined<br>and the signal SIGINT is declared without using grep or any \
<br>equivalent; they should trace through the include files \
visually.&nbsp;&nbsp;If<br>they return with the correct answers and aren't disgusted \
with the<br>mess under /usr/include, slap some pointy hair on \
them.<br><br></blockquote> </div><br>Yes I agree, they are even larger under S.L.E.D. \
10, I believe like 35 MB, or some such.<br>IMHO organizing header files. <br><br>As \
far as the above &quot;exercise&quot; no way w/o grep would I in a million years \
wanna go through <br>/usr/include in a *nix system.<br><br clear="all"><br>



[prev in list] [next in list] [prev in thread] [next in thread]