On Wed, 27 Jan 1999, Matthew Dillon wrote:
>
> :> then we need to update sytle(9) to reflect that.
> :>
> :> In fact, style(9) should say:
> :>
> :> If at all possible, your code should compile without warnings
> :> when the gcc -Wall flag is given.
> :
> :I disagree. As has been shown many times in the past (and I suspect the
> :down-under constituent will show that at least a couple of the
> :'warnings' fixes will be wrong and hide bogus code), making -Wall a goal
> :causes people to cover up bad code with bad casts and such.
> :
> :'-Wall' is *NOT* a good design goal.
>
> Nonsense. -Wall does *NOT* contribute to a bad programmer programming
> badly, and I found at least three fairly serious mistakes when I turned
> it on.
>
> I mean, come on... by your argument the compiler might as well give up
> and not bother warning you about anything!
And for the exact antithesis of silence, TenDRA has the most wonderful warnings,
and it's a great free linter (but does its job better than standard lint),
while producing as good code as GCC most of the time. That takes not into
account once when I ran into some glaring bugs in the compilation, but at
least the warnings were correct :)
>
> -Matt
> Matthew Dillon
> <dil...@backplane.com>
>
> :Nate
> :
> :To Unsubscribe: send mail to majord...@freebsd.org
> :with "unsubscribe freebsd-current" in the body of the message
> :
>
>
> To Unsubscribe: send mail to majord...@freebsd.org
> with "unsubscribe freebsd-current" in the body of the message
>
Brian Feldman _ __ ___ ___ ___
gr...@unixhelp.org _ __ ___ | _ ) __| \
http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) |
FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message
