From owner-freebsd-chat Sun Aug 10 10:39:21 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA01982 for chat-outgoing; Sun, 10 Aug 1997 10:39:21 -0700 (PDT) Received: from kithrup.com (kithrup.com [205.179.156.40]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id KAA01974 for ; Sun, 10 Aug 1997 10:39:19 -0700 (PDT) Received: (from sef@localhost) by kithrup.com (8.6.8/8.6.6) id KAA17243; Sun, 10 Aug 1997 10:39:19 -0700 Date: Sun, 10 Aug 1997 10:39:19 -0700 From: Sean Eric Fagan Message-Id: <199708101739.KAA17243@kithrup.com> To: chat@freebsd.org Subject: Re: variable sized arrays and gcc Newsgroups: kithrup.freebsd.chat In-Reply-To: <199708100752.CAA01811.kithrup.freebsd.chat@dyson.iquest.net> References: <199708100722.DAA03236@skynet.ctr.columbia.edu> from Bill Paul at "Aug 10, 97 03:22:28 am" Organization: Kithrup Enterprises, Ltd. Sender: owner-freebsd-chat@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >> Is this a side-effect of GNU C and GNU C++ being joined together at >> the hip, or did I just miss a memo somewhere? >I don't know if it is a direct side-effect of GNU C and C++ using the >same backend -- however GCC has some really interesting features that >could tend to lock-in the lazy programmer... It has ranges for >switch statements, it can take the address of code labels, it has >some really neat built-ins, etc... gcc has had variable sized arrays since '88, I believe. The feature will now make it into the next ANSI C version. (Along with a bunch of stuff that is *WRONG* and *EVIL*. But this particular feature I happen to like.)