From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <009101bffe36$46c26fa0$02a7b6c3@lucid.proweb.net>
From: "Matt" <matt@proweb.co.uk>
To: <9fans@cse.psu.edu>
References: <200008032020.QAA06704@cse.psu.edu> <398AE743.D94BF48B@arl.army.mil>
Subject: Re: [9fans] ugrading edition 2 graphics to edition 3
Date: Fri,  4 Aug 2000 18:06:03 +0100
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Topicbox-Message-UUID: f6d5a044-eac8-11e9-9e20-41e7f4b1d025

> geoff@x.bell-labs.com wrote:
> > If the original wheel was square or triangular,
> > it's well worth reimplementing it, and you
> > usually learn something along the way.
>
> But if I need a tire for my car, telling me that I have
> to build my own rubber factory etc. just because you
> don't like the tread patterns on existing commercial
> products is absurd.

reducto ad absurdium

IIRC

the romans they are leaving their house?

Formula 1 teams don't get their tyres (note spelling) from Kwik-Fit
They hire the manufacturer to make them specialised tyres.

If you are happy with remoulds then put your includes in every file.

If you want to follow the plan9 program put them in main.h

For my money putting them all in one place feels better because I can see
them all at once.

I can see the argument for putting them in modules that require the
particular includes.

As anecdotal evidence I've taken over the maintenance of a big web site
It's in php and this has various includes dribbled throughout the pages.
The code is bad enough anyway but the web of interdependence is horrible.
Take out one file and one bit of script down the list suddenly falls apart
because it was relying on an include higher up etc.

I'm sure this must be true of a big C project too.


If the includes were at the top of the tree you can see what's needed for
stuff to work and also you can prune them a bit easier.

Matt