Here's how I might have done it if I were using iterators (which uses an explicit stack that the solutions in the referenced document in the OP avoid):
sub samefringe { my ( $x, $y ) = map { fringe_iter($_) } @_; my ( $next_x, $next_y ); while ( 1 ) { ( $next_x, $next_y ) = ( $x->(), $y->() ); last unless $next_x and $next_y; return unless $next_x eq $next_y; } return ( $next_y || $next_y ) ? 0 : 1; } sub fringe_iter { my $list = shift; my @arr = @$list; sub { while (1) { my $reftype = ref($arr[0]); return shift @arr unless $reftype; unshift @arr, fringe_iter(shift @arr) if $reftype eq 'ARRAY'; my $next = $arr[0]->(); if ( $next ) { unshift @arr, $next; } else { shift @arr; } } } }

In reply to Re^2: No Iterators Allowed by runrig
in thread No Iterators Allowed by runrig

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.