Re: Semicolons (Re: Low-Rent Syntax)

Bart Massey <bart@videovax.tv.tek.com>
26 Aug 90 23:07:14 GMT

          From comp.compilers

Related articles
Semicolons (Re: Low-Rent Syntax) bart@videovax.tv.tek.com (Bart Massey) (1990-08-13)
Re: Semicolons (Re: Low-Rent Syntax) codex!peterd@uunet.UU.NET (1990-08-20)
Semicolons (Re: Low-Rent Syntax) thomasm@llama.ingres.com (1990-08-22)
Re: Semicolons (Re: Low-Rent Syntax) trt@rti.rti.org (1990-08-24)
Re: Semicolons (Re: Low-Rent Syntax) mjr@decuac.DEC.COM (1990-08-25)
Re: Semicolons (Re: Low-Rent Syntax) bart@videovax.tv.tek.com (Bart Massey) (1990-08-26)
Re: Semicolons (Re: Low-Rent Syntax) elsie!ado@uunet.UU.NET (1990-08-27)
Re: Semicolons (Re: Low-Rent Syntax) anw@maths.nott.ac.uk (1990-08-29)
Re: Semicolons (Re: Low-Rent Syntax) liam@cs.qmw.ac.uk (1990-09-03)
Re: Semicolons (Re: Low-Rent Syntax) firth@sei.cmu.edu (1990-09-05)
Re: Semicolons (Re: Low-Rent Syntax) lins@apple.com (Chuck Lins) (1990-09-05)
Re: Semicolons (Re: Low-Rent Syntax) rob@baloo.eng.ohio-state.edu (1990-09-05)
[4 later articles]
| List of all articles for this month |

Newsgroups: comp.compilers
From: Bart Massey <bart@videovax.tv.tek.com>
Keywords: C, debuf, design
Organization: Tektronix TV Measurement Systems, Beaverton OR
References: <9008202341.AA06543@llama.ingres.com> <4032@rtifs1.UUCP> <3263@decuac.DEC.COM>
Date: 26 Aug 90 23:07:14 GMT

In article <3263@decuac.DEC.COM> mjr@decuac.DEC.COM (Marcus J. Ranum) writes:
...
> I can imagine building such capabilities into a pre-processor of some sort,
> that did idiot checking based on some information about the kind of things
> you wanted to do, but I don't think it belongs in the compiler (please!).
...


I, on the other hand, am quite happy with the general direction GNU CC has
taken, which is to provide a bunch of warnings for the kinds of suspect
constructs discussed in the above-referenced articles (although nothing that
clever, yet), but to require that the warnings be seperately and explicitly
enabled with compile-time switches. Thus, I tend to use these things the
way I use lint, which is to turn them on only when I really can't understand
why some code is broken, and have been staring at it for hours. Often, GCC
or lint will point out a legal but questionable line of code which will
suddenly make the whole problem clear to me -- especially if I was trying to
read someone else's code :-)...


Bart Massey
..tektronix!videovax.tv.tek.com!bart
..tektronix!reed.bitnet!bart
--


Post a followup to this message

Return to the comp.compilers page.
Search the comp.compilers archives again.