Re: A lesson for compiler warning writers

To pick up on the flame bait, there *are* perfectly good reasons for
compiler warnings, even in a new language. For (purely hypothetical)
instance:


"Argument type declaration is not strictly accurate.
Arithmetic error will occur if x = 0"


"I failed to prove that this loop terminates."


"This declaration shadows a library function."


"Indentation pattern doesn't match bracketting."


You really do want to design a language with some slack in it;
there's nothing to STOP you making all of the above errors, but is
that really what you'd want?
----------------------------------------------------------------------
stephen p spackman stephen@estragon.uchicago.edu
            from july 01 spackman@dfki.uni-sb.de
--

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