On Nov 2, 2007 10:19 AM, Abigail <abig...@abigail.be> wrote:
> On Fri, Nov 02, 2007 at 06:05:11AM +0100, A. Pagaltzis wrote:
> > * Chris Devers <cdev...@pobox.com> [2007-11-02 04:55]:
> > > Anything beyond rudimentary find has always scared me into
> > > laziness.
> >
> > Would that every system I touch had Perl and the File::Find::Rule
> > module installed. Given
> >
> > alias ffr='perl -MFile::Find::Rule'
> >
> > Michael's original example would be
> >
> > ffr -e'unlink find->name("*.txt")->in(".")'
>
>
> File::Find confuses me.
>
> If I have the need to use a find like functionality from within a
> Perl program, I will *always* shell out and use find instead of
> using File::Find.
I'm curious what confuses you about it?
Note that isnt hateful, but it never struck me as confusing.
Although i do recall being shocked at how slow it was to do on a
windows box over a network share. But then i learned that that was due
to windows/Perl stupidity meaning that Perl would open EVERY DANG FILE
just so it could get one field for stat that ive never seen anybody
use on a windows box anyway. (Hence the introduction of
${^WIN32_SLOPPY_STAT} in later versions of perl).
I could never decide who to hate more about that actually, Windows for
not making the field populatable from a mere stat or what windows
calls a stat, or activestate for defaulting to doing the extra work to
populate it despite its virtual non use for cultural reasons.
Yves
--
perl -Mre=debug -e "/just|another|perl|hacker/"
