an hour later oO
I don't like that there are still wrong moves possible*, probably because I din't follow my own concept...
use strict;
use warnings;
use Data::Dump qw/pp dd/;
my $goal = [3,1];
my ($nl,$nr) = @$goal;
my @results;
pathfinder( [0,0] ); # start
pp \@$_ for @results;
sub pathfinder {
my ( $last )=@_;
my ($l,$r) = @$last ;
if ( $nl == $l ) {
if ($nr == $r){
push @results,[ reverse @_];
}
else {
#warn "wrong",pp \@_;
return
}
}
# left
pathfinder( [$l+1,$r ], @_ ) if $l != $nl;
# right
pathfinder( [$l+1,$r+1], @_ ) if $nr != $r;
}
[[0, 0], [1, 0], [2, 0], [3, 1]]
[[0, 0], [1, 0], [2, 1], [3, 1]]
[[0, 0], [1, 1], [2, 1], [3, 1]]
*) i.e. the else branch with the warning should never be reached.
update
solution here
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.