Perhaps you want something like this: 

#!/usr/bin/perl
use warnings;
use strict;

my $infile  = $ARGV[ 0 ];
my $outfile = "sliced_$infile";

open my $INFILE,  '<', $infile  or die "Cannot open '$infile' $!";
open my $OUTFILE, '>', $outfile or die "Cannot open '$outfile' $!";

my %flights;
while ( <$INFILE> ) {
    my ( $hour, $rest ) = /(\d+):\d+(.+)/;
    push @{ $flights{ $hour } }, $rest;
    }

for my $hour ( keys %flights ) {
    my $interval = 60 / @{ $flights{ $hour } };
    for my $i ( 0 .. $#{ $flights{ $hour } } ) {
        printf $OUTFILE "%02d:%02d%s\n", $hour, $i * $interval, $fligh
+ts{ $hour }[ 0 ];
        }
    }

__END__

[download]

In reply to Re: generalisation of a script by jwkrahn
in thread generalisation of a script by steph_bow

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.