In addition to what soonix posted about chomping newlines a recommendation for troubleshooting and general validation is to use file tests to check for the existence of files. They can save you a lot of hair pulling in this situation. 

foreach my $file (@files) {
    if( -f $file) {
        print "<$file> is a plain file.\n";
    }
    else {
        print "<$file> is not a plain file.\n";
    }
}

[download]

This can be shortened with the conditional operator:

use strict;
use warnings;

my @files = qw( file1 test.pl.txt file3 4);
push @files, "file5
";

foreach my $file (@files){
    print "<$file> is ", -f $file ? '' : 'not ', "a plain file.\n";
}

[download]

I encourage you to consider using strict also.

In reply to Re: creating valid paths for Path::Tiny by Lotus1
in thread creating valid paths for Path::Tiny by Aldebaran

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.