Date: Sun, 7 Jun 1998 15:21:29 -0500 (CDT) From: Joel Ray Holveck <joelh@gnu.org> To: dufault@hda.com Cc: moncrg@ma.ultranet.com, mph@pobox.com, mike@smith.net.au, hackers@FreeBSD.ORG Subject: Re: Irritating cpp feature Message-ID: <199806072021.PAA18398@detlev.UUCP> In-Reply-To: <199806071601.MAA13243@hda.hda.com> (message from Peter Dufault on Sun, 7 Jun 1998 12:01:54 -0400 (EDT)) References: <199806071601.MAA13243@hda.hda.com>
next in thread | previous in thread | raw e-mail | index | archive | help
>> you can put anything you want in an #if 0/#endif block. >> by definition, the preprocessor deletes such before the compiler >> (which is the only thing that checks code syntax) >> even sees it > Not true according to info gcc. However, -traditional > works around it: > The best solution to such a problem is to put the text into an > actual C comment delimited by `/*...*/'. However, `-traditional' > suppresses these error messages. Note that with gcc 2.8, you may prefer -traditional-cpp. This does have some other syntactic implications, of course. Happy hacking, joelh -- Joel Ray Holveck - joelh@gnu.org - http://www.wp.com/piquan Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped 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?199806072021.PAA18398>