Why no warnings when re-assigning builtin names?

[Seebs]

On 2011-08-16, Ethan Furman <ethan at stoneleaf.us> wrote:
> Seebs wrote:
>> The quality of C code I have to deal with has increased dramatically as
>> gcc's aggressive use of warnings has spread.

> With gcc you pay the cost once, with Python you would pay it with every 
> run.  A linter would be more along the lines of 'pay it once'.

Huh!

That is a really good point, which I had not considered.  I still prefer
to get warnings, but... Hmm.

I wonder whether there's a way to mitigate the cost of these things by
messing with -W settings, such that runtime that wants to be fast can
omit the checks, but the default could still be to, well, prevent likely
errors.

-s
-- 
Copyright 2011, all wrongs reversed.  Peter Seebach / usenet-nospam at seebs.net
http://www.seebs.net/log/ <-- lawsuits, religion, and funny pictures
http://en.wikipedia.org/wiki/Fair_Game_(Scientology) <-- get educated!
I am not speaking for my employer, although they do rent some of my opinions.