Glad I could help. A couple comments though, you probably want to initilize @schedule with an empty list. 
@schedule = ();

The other is you usually don't want to assign to @_, depending on the context it might cause subtle bugs. @_ has some magic associated with it. For instance, in a sub, @_ acts as aliases to the passed arguments. (Example below)

It appears assigning to @_ makes it lose it's magic so I don't think it is a problem here but it's probably a dubious habit to form. 

#!/usr/bin/perl -w

use strict;

my ($foo,$bar,$baz) = (1,2,3);

print "$foo, $bar, $baz \n"; # Prints 1, 2, 3

foo($foo,$bar,$baz);

print "$foo, $bar, $baz \n"; # Prints 5, 10 , 15


sub foo {
    foreach (@_) {
        $_ *= 5;
    }
}

[download]
-Lee

"To be civilized is to deny one's nature."

In reply to Re: Re: Re: foreach within a foreach by shotgunefx
in thread foreach within a foreach by Spenser

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.