From owner-freebsd-hackers Thu Jan 29 00:26:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA28599 for hackers-outgoing; Thu, 29 Jan 1998 00:26:07 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from word.smith.net.au (vh1.gsoft.com.au [203.38.152.122]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA28590 for ; Thu, 29 Jan 1998 00:26:02 -0800 (PST) (envelope-from mike@word.smith.net.au) Received: from word (localhost [127.0.0.1]) by word.smith.net.au (8.8.8/8.8.5) with ESMTP id SAA02281; Thu, 29 Jan 1998 18:49:07 +1030 (CST) Message-Id: <199801290819.SAA02281@word.smith.net.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: joelh@gnu.org cc: freebsd-hackers@FreeBSD.ORG Subject: Re: GCC extentions in FreeBSD code In-reply-to: Your message of "Thu, 29 Jan 1998 02:20:49 MDT." <199801290820.CAA04981@detlev.UUCP> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 29 Jan 1998 18:49:07 +1030 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe hackers" > What's the policy on using GCC extentions in kernel code? In > particular, I'm considering using typeof for some variables that are > holders for other variables, so that if the structures ever change, my > code will change along with it. Don't do it. Define and export a type if you're implementing a public interface. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\