Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!uwm.edu!gem.mps.ohio-state.edu!usc!snorkelwacker!spdcc!ima!haddock!karl
From: karl@haddock.ima.isc.com (Karl Heuer)
Newsgroups: comp.lang.c
Subject: Re: This one bit me today
Message-ID: <15014@haddock.ima.isc.com>
Date: 27 Oct 89 21:34:47 GMT
References: <2739@hub.UUCP> <14811@bfmny0.UU.NET>
Reply-To: karl@haddock.ima.isc.com (Karl Heuer)
Organization: Interactive Systems, Cambridge, MA 02138-5302
Lines: 13

In article <14811@bfmny0.UU.NET> tneff@bfmny0.UU.NET (Tom Neff) writes:
>>The best solution would be to have /* /* */ generate a warning.
>
>Again -- this is a common usage in config.h type files.
>	/* #define BSD4_3  /*  for BSD 4.3 systems  */

The best solution is for this to be an option.  Then people who use the above
grotesqueness can disable the warning, and those of us who use a more sensible
style can enable it and have the benefit of the improved error checking.

The same applies to `if (a=b)'.

Karl W. Z. Heuer (ima!haddock!karl or karl@haddock.isc.com), The Walking Lint