perldoc -f glob for starters.

It'll just do what you think it should.

e.g. 

globfoo
=======

#!/usr/bin/perl -w

my @files = glob("foo*/ba*/");
print join "\n", @files, "\n";

mothra@penderel:~/src/Perl$ ls -d foo*/ba*/
foo1/bar1/  foo1/bar2/  foo1/bar3/  foo2/baz2/  foo2/baz3/

mothra@penderel:~/src/Perl$ ./globfoo
foo1/bar1/
foo1/bar2/
foo1/bar3/
foo2/baz2/
foo2/baz3/

[download]

etc.

It's probably a bad idea to roll your own logfile implementation (i.e. you could be learning lots of *other* things besides trying to make a wheel more round), but alas, to each their own.

In reply to Re: parsing directory glob in config file by mothra
in thread parsing directory glob in config file by gnu@perl

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.