Compiler bug

[Thomas Lindgren]

>Is there a up to date version of the guard expression description ?
>Page 29-30 (Concurrent programming in erlang 2:nd edtion) lists most
typechecks,
>comparision and bifs allowed.
>Erlang Extensions Since 4.4 (html docs) mentions the record/2 and
function/1
>typecheck, but where is is_list/1 and the use of "and", "or", and "not"
>mentioned ?

Perhaps it is time to raise the question whether there
are getting to be too many similar operations in Erlang as well?

For guards, we have comma, semicolon (or), and, or, not.
(Could we merge some operations here?)

For guard operations, we have type(X) and is_type(X).
(Could this be unified into just type(X)?)

For expressions, we have and, or, andalso, orelse.
(Do people use "E1 and E2" while relying on E2 being
evaluated when E1 is false? If not, rename andalso into and,
etc.)

What do you think?

Best,
Thomas