Subject: Re: includes pulling in what they need?
To: Hubert Feyrer <hubert.feyrer@rz.uni-regensburg.de>
From: Frank van der Linden <frank@wins.uva.nl>
List: tech-net
Date: 12/08/1998 14:03:11
On Mon, Dec 07, 1998 at 01:09:06AM +0100, Hubert Feyrer wrote:
> 
> In general, everything that needs some definitions made in another file
> would be optimal. I've stumbled across netinet/ip.h wanting type n_time,
> which I found to be defined in netinet/in_systm.h today, and it's probably
> some others.  (And I guess I better don't ask that source level
> compatibility w/ some penguin driven OS would be nice in that area - but
> then what do I know about anything of either's network programming :-/)

Well.. if our header files require including some other, obscure
include files, while this is not needed on several (not just one)
systems, then they should probably be fixed. But it is normal practice
that an include file requires the inclusion of another, it would be wrong
to bloat all include files just because you can't compile Linux source
out of the box. Unfortunately, there seems to be quite a bit of software
written on Linux that isn't very portable.

- Frank