Binary match in function head doesn't compile - Erlang Programming

The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Message from discussion Binary match in function head doesn't compile
Received-SPF: pass (google.com: domain of erlang-questions-boun...@erlang.org designates 192.121.151.104 as permitted sender) client-ip=192.121.151.104;
Date: Sat, 27 Oct 2012 12:34:39 +1100
From: Jeff Schultz <j...@csse.unimelb.edu.au>
To: Erik Pearson <e...@defunweb.com>
Message-ID: <20121027013439.GA15...@mulga.csse.unimelb.edu.au>
References: <CA+dr1pvhSwe2ZVwVREdzFH1c2yPVuVqRUfNx=_xaS24D-4C...@mail.gmail.com>
MIME-Version: 1.0
Content-Disposition: inline
In-Reply-To: <CA+dr1pvhSwe2ZVwVREdzFH1c2yPVuVqRUfNx=_xaS24D-4C...@mail.gmail.com>
User-Agent: Mutt/1.5.16 (2007-06-09)
Cc: erlang-questions Questions <erlang-questi...@erlang.org>
Subject: Re: [erlang-questions] Binary match in function head doesn't	compile
Precedence: list
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: erlang-questions-boun...@erlang.org
Sender: erlang-questions-boun...@erlang.org

On Fri, Oct 26, 2012 at 11:27:06AM -0700, Erik Pearson wrote:
> test(<<Field:Len/binary, Rest/binary>>, Len) ->
>     {Len, Field, Rest}.

> does not compile, complaining that "variable 'Len' is unbound", while this

Short answer: Erlang isn't a general constraint solver.

> test(<<Field:2/binary, Rest/binary>>, Field) ->
>     {Field, Rest}.

> does. For some reason the compiler doesn't see the Len from the match spec
> in the arguments, but it does see Field. Is that by design?

That depends on what you mean by "see."  It actually treats that clause
as if it were something like

    test(<<Field:2/binary, Rest/binary>>, Arg2),
    	Field = Arg2
    ->
	{Field, Rest}.

(Which is not Erlang, but I hope you get the idea.)

And, of course, your problem clause looks like

    test(<<Field:Len/binary, Rest/binary>>, Arg2),
        Len = Arg2
    ->
	{Len, Field, Rest}.

which makes clear why the compiler sees Len as unbound when used in
the pattern match.

It's obviously easy to re-arrange the data-flow to make this sort of
thing compilable.  I wouldn't expect to run across a need for it in
practice though.


    Jeff Schultz
_______________________________________________
erlang-questions mailing list
erlang-questi...@erlang.org
http://erlang.org/mailman/listinfo/erlang-questions
Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
Account Options
