From owner-freebsd-chat Sun Aug 10 20:34:59 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id UAA05795 for chat-outgoing; Sun, 10 Aug 1997 20:34:59 -0700 (PDT) Received: from ethanol.gnu.ai.mit.edu (devnull@ethanol.gnu.ai.mit.edu [128.52.46.64]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id UAA05790 for ; Sun, 10 Aug 1997 20:34:57 -0700 (PDT) Received: by ethanol.gnu.ai.mit.edu (8.8.5/8.6.12GNU) id XAA04779; Sun, 10 Aug 1997 23:34:36 -0400 Date: Sun, 10 Aug 1997 23:34:36 -0400 Message-Id: <199708110334.XAA04779@ethanol.gnu.ai.mit.edu> From: "Joel N. Weber II" To: sef@Kithrup.COM CC: chat@FreeBSD.ORG In-reply-to: <199708101740.KAA17289@kithrup.com> (message from Sean Eric Fagan on Sun, 10 Aug 1997 10:40:59 -0700) Subject: Re: variable sized arrays and gcc x-url: http://www.red-bean.com/~nemo x-attribution: nemo x-foobar: If you can distinguish between good and bad advice, you don't need advice. Sender: owner-freebsd-chat@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Variardic macros and 'inline' are also going to be in the next ANSI C standard. About time to standardize `inline'; I've been using it in my portable code for a while. (OTOH, I rely on autoconf to do `#define inline' on compilers that don't support it.)