From owner-freebsd-hackers Fri Aug 7 13:22:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA13649 for freebsd-hackers-outgoing; Fri, 7 Aug 1998 13:22:57 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from tim.xenologics.com (tim.xenologics.com [194.77.5.24]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA13631 for ; Fri, 7 Aug 1998 13:22:49 -0700 (PDT) (envelope-from seggers@semyam.dinoco.de) Received: (from uucp@localhost) by tim.xenologics.com (8.8.5/8.8.8) with UUCP id WAA06225; Fri, 7 Aug 1998 22:21:10 +0200 (MET DST) Received: from semyam.dinoco.de (semyam.dinoco.de [127.0.0.1]) by semyam.dinoco.de (8.8.8/8.8.8) with ESMTP id VAA15427; Fri, 7 Aug 1998 21:49:34 +0200 (CEST) (envelope-from seggers@semyam.dinoco.de) Message-Id: <199808071949.VAA15427@semyam.dinoco.de> To: Terry Lambert Subject: Re: C and static initialization with unions In-reply-to: Your message of "Fri, 07 Aug 1998 01:33:05 -0000." <199808070133.SAA24688@usr06.primenet.com> Cc: seggers@semyam.dinoco.de, freebsd-hackers@FreeBSD.ORG Date: Fri, 07 Aug 1998 21:49:34 +0200 From: Stefan Eggers Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Is it allowed in FreeBSD? Is all FreeBSD C source code portable? > > Good question; I don't know the answer. We have at least a little bit of unportable code in swap_pager.c where arrays of runtime computed size (array size depends on one of the parameters of the function) get used. Works great with gcc but not with an unsuspecting ANSI C compiler. What's the official opinion on using gcc extensions? Should this have been avoided or is it OK to use them in the kernel? Stefan. -- Stefan Eggers Lu4 yao2 zhi1 ma3 li4, Max-Slevogt-Str. 1 ri4 jiu3 jian4 ren2 xin1. 51109 Koeln Federal Republic of Germany To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message