Guard sequences, short circuit boolean operators
Mon Feb 7 19:24:36 CET 2005
I just wonder why andalso and orelse aren't allowed in guard sequences.
Even in the case of backward compatibility it makes no sense, they are
just equal to the normal "and" and "or" (ignoring precedence rules ...)
as far as I understand the reference manual correctly. I just want to
know the reason for this ... - in my humble opinion it looks a bit weird
using andalso in one place and being forced to use and in another place
to have the same thing (or using a "," which I assume is something left
from the days when Erlang was running in a Prolog system?).
More information about the erlang-questions