[erlang-questions] Compiler warnings on impossible constructs?

[Arjan Scherpenisse]

Hi list,

I today fixed a stupid bug in something I wrote last week, namely, an 
atom-to-atom comparison which should have been a variable-to-atom 
comparioon:

It read: foo =:= bar while it should have read Foo =:= bar.

So, my question is, can't Erlang detect this kind of situations on 
compile time? Obviously, the expression foo =:= bar will never be true, 
right?

Or maybe I just trust flymake to much instead of doublechecking the 
stuff I write.. ;)

Arjan


-- 
Arjan Scherpenisse ----- New media art, research, development
arjan@REDACTED +31641322599 - http://scherpenisse.net