Probably because you used split with an expression that were empty or contained only newlines \n here:

@split_hit_non_barrel=split(/\n/, $separate_hit_non_barrel);
[download]

Since split absorbs its seperators, it would then return an empty list.
The first entry of an empty array would give an undef value:

$hit_line_non_barrel=$split_hit_non_barrel[0];
[download]

Using an undef value for a match would give a warning then:

$hit_line_non_barrel=~/^(.*?)\s+/
[download]

This is just guessing, using the Perl debugger would be much better. You can even customize the debugger, so it stops right at the point when the warnings occurs -> Re: Debugging a program and Re^3: Debugging a program allowing you to look what has gone wrong while having the whole context available. I am using this regularly with my code.

---

---

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! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

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:
	&		&
	<		&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.