I am not sure what the solution to your specific problem is, but you should consider the following:

There is at least 1 typo in your posted code. use CGI needs a semicolon.

Using the strictures can help prevent other simple mistakes: 

use warnings;
use strict;

[download]
This will force you to declare all yor variables using my, which will be well worth the effort and time.

The following line looks odd: 

@line = pop(@line);

[download]
pop actually modifies the array.

The following line also looks odd: 

$inum = ++$inum;

[download]
++$inum may be sufficient.

Declaring a sub in the middle of your main code is a little confusing.

Your sub indexArray, while it may earn you a low Perl golf score, should probably not be so compact. It would benefit greatly by some added whitespace.

I hope this helps.

In reply to Re: specifying path to files by toolic
in thread specifying path to files by jvallee

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.