From owner-freebsd-hackers  Tue Jan  7 14:43:09 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.4/8.8.4) id OAA16741
          for hackers-outgoing; Tue, 7 Jan 1997 14:43:09 -0800 (PST)
Received: from profane.iq.org (profane.iq.org [203.4.184.217])
          by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id OAA16727
          for <hackers@freebsd.org>; Tue, 7 Jan 1997 14:42:45 -0800 (PST)
Received: (from proff@localhost)
          by profane.iq.org (8.8.4/8.8.2) id JAA17826
          for hackers@freebsd.org; Wed, 8 Jan 1997 09:41:31 +1100 (EST)
From: Julian Assange <proff@iq.org>
Message-Id: <199701072241.JAA17826@profane.iq.org>
Subject: #include file xref philosophy
To: hackers@freebsd.org
Date: Wed, 8 Jan 1997 09:41:30 +1100 (EST)
X-Mailer: ELM [version 2.4ME+ PL28 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk


What is the -current philosophy on intra #include file dependencies?

Is there any reason for not following the posix line and having
include files resolve all their own dependencies? I'm talking about
things like <dirent.h> needing the code that includes it, include
<sys/types.h> before hand.

Appart from portability issues, which I am increasingly encountering,
I find the idea that user developed .c code must magically "know"
what each /usr/include/* file needs and in what order very ugly
and ecapsulation breaking.

Moving towards self-resolving is of course backwards compatible.
Can we agree to do this for /usr/include/*? 

Cheers,
Julian.