From owner-freebsd-arch@FreeBSD.ORG Thu Mar 10 19:51:23 2011 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5D21D106564A; Thu, 10 Mar 2011 19:51:23 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id 3492A8FC16; Thu, 10 Mar 2011 19:51:23 +0000 (UTC) Received: from bigwig.baldwin.cx (66.111.2.69.static.nyinternet.net [66.111.2.69]) by cyrus.watson.org (Postfix) with ESMTPSA id C36F846B89; Thu, 10 Mar 2011 14:51:22 -0500 (EST) Received: from jhbbsd.localnet (unknown [209.249.190.10]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 41B378A027; Thu, 10 Mar 2011 14:51:22 -0500 (EST) From: John Baldwin To: freebsd-arch@freebsd.org Date: Thu, 10 Mar 2011 14:46:37 -0500 User-Agent: KMail/1.13.5 (FreeBSD/7.4-CBSD-20110107; KDE/4.4.5; amd64; ; ) References: In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201103101446.37589.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.6 (bigwig.baldwin.cx); Thu, 10 Mar 2011 14:51:22 -0500 (EST) Cc: mdf@freebsd.org Subject: Re: style(9) rules for nested includes X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Mar 2011 19:51:23 -0000 On Thursday, March 10, 2011 12:17:28 pm mdf@freebsd.org wrote: > I recall a recent discussion/PR about nested includes in the context > of and being a few of the only ones > allowed. However, I don't see anything in style(9) about this. bde@ is probably the most authoritative. My understanding is that the only nested includes allowed in sys/sys/*.h are the two listed above and any header that starts with an underscore (sys/_mutex.h, etc.). The underscore variants were added to allow nested includes when absolutely necessary, but those includes are the bare minimum required to define structures, etc. > Now we come to the reason I ask. I'm working on a patch to change the > static sysctl code to use the standard SYSININT/SYSUNINIT code rather > than have special treatment in kern_linker.c, but to do this I need to > either change quite a few places that include , or > include instead of in sysctl.h, as > the SI_SUB_SYSCTLS value isn't visible otherwise. Hmm, what is the reason to use SYSINIT's instead of a dedicated linker set? -- John Baldwin