That solution isn't terribly efficient, however, since the entire array (which is specified as being huge) has to be rewritten for every splice. You're splicing from the start, not the end, and might do better splicing in reverse and then reversing. Alternately, you could make a copy of the array contents instead of splicing: 
use strict;
use warnings;

my (@arr, @arr2, $i);

$arr[$_] = $_ for 0..357;

for ($i = 0; $i <= $#arr; $i += 50) {
    push @arr2, [@arr[$i..($i+49)]];
}
$#{$arr2[$#arr2]} = $#arr % 50;

print join(' ', @$_), "\n" for @arr2;

[download]
Yes, this has a memory cost twice that of the original array, but you're going to need that even with the spliced solution, since I don't believe the extra space is returned to the script as the array is reduced in size?

In reply to Re: splitting arrays by TedPride
in thread splitting arrays by Anonymous Monk

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.