Erlang: Danger of Mixing Records and Tuples

I received an error from the erlang compiler: “Warning: this clause cannot match because a previous clause at line 387 always matches” and was staring at the code trying to figure out why the top clause was a ‘catch all’.

case Result of
    {Version, NewId, ConnectionStates, NextProtocol} ->
        ....
    #alert{} = Alert ->
        ....

so #alert has 3 fields so is always matched by the 4 field tuple.

Like this:

Be the first to like this post.

This entry was posted on November 13, 2011 at 5:02 pm and is filed under Uncategorized. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.