From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <52af7b0e92c11760a5b9d627fd71aa09@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Include guards and multiple includes
Date: Fri, 20 Oct 2006 19:15:05 -0400
From: geoff@plan9.bell-labs.com
In-Reply-To: <219D85AA-959D-464C-90C2-0F132809F0B9@telus.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Topicbox-Message-UUID: cf92f85c-ead1-11e9-9d60-3106f5b1d025

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.