Date: Wed, 5 Jan 2000 14:54:35 -0500 (EST) From: Thomas David Rivers <rivers@dignus.com> To: cracauer@cons.org, rfg@monkeys.com Cc: hackers@FreeBSD.ORG Subject: Re: [OFFTOPIC] alt. C compiler Message-ID: <200001051954.OAA32472@lakes.dignus.com> In-Reply-To: <1468.947101812@monkeys.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> > > In message <20000105100716.A63545@cons.org>, > Martin Cracauer <cracauer@cons.org> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200001051954.OAA32472>