From owner-freebsd-hackers Wed May 8 12: 9:30 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from damnhippie.dyndns.org (12-253-177-2.client.attbi.com [12.253.177.2]) by hub.freebsd.org (Postfix) with ESMTP id 0454237B407 for ; Wed, 8 May 2002 12:09:09 -0700 (PDT) Received: from [172.22.42.2] (peace.hippie.lan [172.22.42.2]) by damnhippie.dyndns.org (8.11.6/8.11.6) with ESMTP id g48J98G76591 for ; Wed, 8 May 2002 13:09:08 -0600 (MDT) (envelope-from freebsd@damnhippie.dyndns.org) User-Agent: Microsoft Outlook Express Macintosh Edition - 5.01 (1630) Date: Wed, 08 May 2002 13:09:14 -0600 Subject: Re: /usr/include/netinet/in.h From: Ian To: freebsd-hackers Message-ID: In-Reply-To: <3CD9727B.B53067A4@mindspring.com> Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > The general rule is "including includes from includes is bad". Okay, it's time to point out that these are opinions, not rules, and differing opinions exist. My opinion is that if a given header file requires some aspect of another interface, that header should (nay, MUST) include what it needs for itself, rather than relying on something external to "do the right thing". Why require thousands of programmers to remember all these interdependancies as opposed to one programmer encoding the depenancy once where it belongs and then everyone else can get on with their life and get some real coding done. Within the context of a given project (E.G., FreeBSD) someone's opinion on this matter may achieve the force of "a rule". Within the larger context of software engineering in general there is no rule, not even a concensus, on this issue. -- Ian Programmer since 1972 C programmer since 1985 Demagogue since... well, as long as I can remember. :-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message