Hi qazwart

I agree with you and I agree with davorg's suggestion to use File::Find::Rule. The rules can be a bit verbose so I put them in a sub.

#!/usr/bin/perl

use strict;
use warnings;
use File::Find::Rule;

my $dir = 'c:/www/sw/category';

my $rule = get_rule($dir);

while (my $file = $rule->match) {
  print "$file\n";
}

sub get_rule{

  my ($dir) = @_;
  my $rule = File::Find::Rule->new;
  
  $rule->or(
    $rule->new
         ->directory
         ->name(qr/^_/)
         ->prune
         ->discard,
    $rule->new
  );
  
  $rule->name('*.html');
  
  $rule->file->not(
    $rule->new->name('00template.html'),
    $rule->new->name('00greybox.html'),
  );
  
  $rule->start($dir);
  
  return $rule;
}

[download]

In reply to Re: How do you make File::Find a bit less ugly? by wfsp
in thread How do you make File::Find a bit less ugly? by qazwart

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.