From owner-cvs-sys Sun Oct 22 00:15:04 1995 Return-Path: owner-cvs-sys Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id AAA27696 for cvs-sys-outgoing; Sun, 22 Oct 1995 00:15:04 -0700 Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id AAA27680 ; Sun, 22 Oct 1995 00:14:50 -0700 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id QAA23370; Sun, 22 Oct 1995 16:41:03 +1000 Date: Sun, 22 Oct 1995 16:41:03 +1000 From: Bruce Evans Message-Id: <199510220641.QAA23370@godzilla.zeta.org.au> To: jkh@time.cdrom.com, pst@shockwave.com Subject: Re: SYSCALL IDEAS [Was: cvs commit: src/sys/kern sysv_msg.c sysv_sem.c sysv_shm.c] Cc: CVS-commiters@freefall.freebsd.org, bde@freefall.freebsd.org, cvs-sys@freefall.freebsd.org, hackers@freebsd.org, swallace@ece.uci.edu Sender: owner-cvs-sys@freebsd.org Precedence: bulk >Just FYI, it's never been mine. I routinely use structure >initializers that only gcc grocks, and have even been known to do the >occasional: > { > char foo[n]; > .. > } >To do the job of alloca.. Not that I use the latter construct very >often - I generally just use alloca directly, but the point is that if /usr/src/usr.sbin/config/main.c:120: warning: ANSI C forbids variable-size array `tmp' It's a nice feature, but it probably shouldn't be used without ifdefs in a bootstrapping utility, and using ifdefs negates the advantage of having it (you have to write ugly portable code _and_ ugly ifdefs _and_ code using the feature instead of just ugly portable code). Bruce