If it is really dying without error, you should follow the Basic debugging checklist, especially points 2 and 4:

use Data::Dumper;
...
print Dumper \@wsl;
foreach $filename(@wsl)
    {
    warn "trying to open file '$filename'\n";
    open(FIN, $filename)  or die "Could not open file '$filename' $!";
    warn "successfully opened file '$filename'\n";
    while (my $row = <FIN>)
...
[download]

I prefer to put filenames in configuration files¹, e.g. using Config::Tiny.

• The advantage of this approach is that you can put your filenames there totally unchanged, including backslashes, spaces and other special characters.
• Disadvantage: for characters outside the ASCII range you have to use the same encoding (binmode) as your editor (or whatever tool you use to put the filename into the config file).

¹ - obviously this is not feasible for the name of the configuration file itself…

---

---

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.