From owner-freebsd-hackers Wed Jan 5 11:55: 7 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp1.vnet.net (smtp1.vnet.net [166.82.1.31]) by hub.freebsd.org (Postfix) with ESMTP id 2219C14A0D for ; Wed, 5 Jan 2000 11:55:00 -0800 (PST) (envelope-from rivers@dignus.com) Received: from dignus.com (ponds.vnet.net [166.82.177.48]) by smtp1.vnet.net (8.9.1a/8.9.1) with ESMTP id OAA16171; Wed, 5 Jan 2000 14:54:37 -0500 (EST) Received: from lakes.dignus.com (lakes.dignus.com [10.0.0.3]) by dignus.com (8.9.2/8.8.5) with ESMTP id OAA08873; Wed, 5 Jan 2000 14:54:35 -0500 (EST) Received: (from rivers@localhost) by lakes.dignus.com (8.9.3/8.6.9) id OAA32472; Wed, 5 Jan 2000 14:54:35 -0500 (EST) Date: Wed, 5 Jan 2000 14:54:35 -0500 (EST) From: Thomas David Rivers Message-Id: <200001051954.OAA32472@lakes.dignus.com> To: cracauer@cons.org, rfg@monkeys.com Subject: Re: [OFFTOPIC] alt. C compiler Cc: hackers@FreeBSD.ORG In-Reply-To: <1468.947101812@monkeys.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > In message <20000105100716.A63545@cons.org>, > Martin Cracauer wrote: > > >... If you have examples where it breaks, send them to me, please. > > Here is a list of a few system include file problems, in no particular > order. Most of these are ANSI conformance problems. > > > /usr/include/cam/cam.h:153: comma at end of enumerator list > /usr/include/cam/cam_ccb.h:478: comma at end of enumerator list > /usr/include/cam/cam_ccb.h:487: comma at end of enumerator list > /usr/include/cam/cam_ccb.h:494: comma at end of enumerator list > /usr/include/cam/cam_ccb.h:739: comma at end of enumerator list > /usr/include/cam/cam_ccb.h:92: ANSI C restricts enumerator values to range of `int' > /usr/include/cam/cam_ccb.h:97: ANSI C restricts enumerator values to range of `int' > /usr/include/cam/cam_ccb.h:98: comma at end of enumerator list > /usr/include/cam/scsi/scsi_cd.h:132: ANSI C does not allow extra `;' outside of a function > /usr/include/cam/scsi/scsi_targetio.h:48: comma at end of enumerator list > /usr/include/machine/cons.h:8: i386/i386/cons.h: No such file or directory > /usr/include/machine/ipl.h:42: i386/isa/icu_ipl.h: No such file or directory > /usr/include/machine/mpapic.h:33: i386/isa/icu.h: No such file or directory > /usr/include/machine/pcb.h:82: structure has no members > /usr/include/posix4/posix4.h:36: opt_posix.h: No such file or directory > /usr/include/stand.h:311: arguments given to macro `getchar' > /usr/include/sys/chio.h:155: comma at end of enumerator list > /usr/include/sys/namei.h:169: ANSI C forbids zero-size array `nc_name' This begs a question.... and to help in my understanding... Certainly, these header files aren't ANSI conforming. But - that's not to say we don't have an ANSI conforming C implementation, as these aren't ANSI header files - right? That is; isn't it true that in our "own" header files - we can do whatever we want? - Dave Rivers - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message