From owner-freebsd-current Thu May 8 10:57:57 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA10349 for current-outgoing; Thu, 8 May 1997 10:57:57 -0700 (PDT) Received: from bitbox.follo.net (bitbox.follo.net [194.198.43.36]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA10344 for ; Thu, 8 May 1997 10:57:53 -0700 (PDT) Received: (from eivind@localhost) by bitbox.follo.net (8.7.6/8.7.3) id TAA06245; Thu, 8 May 1997 19:56:56 +0200 (MET DST) Date: Thu, 8 May 1997 19:56:56 +0200 (MET DST) Message-Id: <199705081756.TAA06245@bitbox.follo.net> From: Eivind Eklund To: Bruce Evans CC: sos@sos.freebsd.dk, freebsd-current@FreeBSD.ORG, roberto@keltia.freenix.fr In-reply-to: Bruce Evans's message of Thu, 8 May 1997 08:30:53 +1000 Subject: Re: #include problem breaks current References: <199705072230.IAA21803@godzilla.zeta.org.au> Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > >> Could we please get this mess sorted out, I'm sick and tired of all > >> that nitpicking with include files lately :(, is it REALLY nessesary > >> to make us different from the rest of the world ???? > > > >To not have hidden dependencies everywhere? To have include files > >that actually work according to POSIX? > > POSIX generally specifies including yourself. The rpc > headers are not specified by POSIX. What I want is all include > files to work according to ANSI-extended-to-cover-all-include-files. > In particular, include files should neither depend on each other nor > declare each others symbols (either by including each other or directly), > except for a few well documented warty cases like `size_t'. I'll try to go through all the include files and at least document the cases where they depend on each other. Then we can discuss what to do about each case afterwards. Eivind. Sigh. All this fuzz "just to close a PR"...