Date: Fri, 17 Apr 1998 21:30:07 -0700 (PDT) From: Bruce Evans <bde@zeta.org.au> To: freebsd-bugs Subject: Re: bin/6332: time.h doesn't compile with -traditional Message-ID: <199804180430.VAA24939@hub.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR bin/6332; it has been noted by GNATS. From: Bruce Evans <bde@zeta.org.au> To: bde@zeta.org.au, FreeBSD-gnats-submit@FreeBSD.ORG, rivers@dignus.com Cc: Subject: Re: bin/6332: time.h doesn't compile with -traditional Date: Sat, 18 Apr 1998 14:10:35 +1000 >> `const' is used on about 561 lines in /usr/include/*.h, 244 lines in >> /usr/include/sys/*.h, ... It is too late to uglify them all. > > It's too late? I didn't know changes were limited by the calendar :-) >Granted, it may be too late for 2.2.6 (certainly) and likely even 3.0, >but what about future versions? ANSI C has been standard for about 10 years now. BSD4.4 never fully supported K&R 5 years ago (it requires separate libraries compiled with -traditional for compatibility ...), so why should we start now? >> <sys/cdefs.h> defines away `const' (and other ANSI-only keywords) >> unless NO_ANSI_KEYWORDS or __GNUC__ is defined. It is assumed that >> `gcc -traditional' is only used to compile dusty code that uses >> these keywords as normal identifiers. If your code doesn't have >> such identifiers then you can easily define away the identifiers >> directly by compiling with `gcc -traditional -Dconst='. > > Umm... that's not the assumption I was using. You have to read the "documentation" for -traditional support (cdefs.h). Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199804180430.VAA24939>