[erlang-questions] Compiler warnings on impossible constructs?
Wed Jul 3 13:16:27 CEST 2013
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
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,
Or maybe I just trust flymake to much instead of doublechecking the
stuff I write.. ;)
Arjan Scherpenisse ----- New media art, research, development
+31641322599 - http://scherpenisse.net
More information about the erlang-questions