From owner-freebsd-chat Sun Aug 10 01:25:55 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id BAA10150 for chat-outgoing; Sun, 10 Aug 1997 01:25:55 -0700 (PDT) Received: from scanner.worldgate.com (scanner.worldgate.com [198.161.84.3]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA10143 for ; Sun, 10 Aug 1997 01:25:51 -0700 (PDT) Received: from znep.com (uucp@localhost) by scanner.worldgate.com (8.8.5/8.8.5) with UUCP id CAA05379; Sun, 10 Aug 1997 02:25:38 -0600 (MDT) Received: from localhost (marcs@localhost) by alive.znep.com (8.7.5/8.7.3) with SMTP id WAA25764; Sat, 9 Aug 1997 22:25:13 -0600 (MDT) Date: Sat, 9 Aug 1997 22:25:12 -0600 (MDT) From: Marc Slemko To: Bill Paul cc: chat@FreeBSD.ORG Subject: Re: variable sized arrays and gcc In-Reply-To: <199708100722.DAA03236@skynet.ctr.columbia.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-chat@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sun, 10 Aug 1997, Bill Paul wrote: > 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? gcc has a lot of "features". Sometimes they are helpful, sometimes they are stupid, nearly always they are annoying if you get used to useing them then stop using gcc. Nested functions, typeof(), macros with variable args (I _really_ wish this was standard sometimes...), inline functions... the list goes on and on. I would be willing to bet you could write a short program using some of gcc's extensions that would look crazy to a good ANSI C programmer.