Bitten by regular expression syntax.
next if $FILE =~ /^./;
Should be:
next if $FILE =~ /^\./;
In your match you were looking for each filename starting with, not a 'dot', but any single character. Naturally everything matched. Easily done.
Update:
Turns out you have a few other issues. As
Corian says, you need to prefix $FILE with the directory name. There is another issue as well - for some reason you require a reference to an array to be passed to your subroutine (why?). Here are the relevant lines modified:
if(-d "$FILEPATH/$FILE"){
#Don't wanna have current directory and the one below
next if $FILE =~ /^\./;
push(@FILELIST,@{readin_directory(["$FILEPATH/$FILE"])}
+);
}
I have not tested this on a wide range of naming conventions. Notice that the argument to the subroutine call (& not required) is in square brackets, to generate a ref to an array.
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.