Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!wuarchive!cs.utexas.edu!swrinde!elroy.jpl.nasa.gov!jpl-devvax!lwall
From: lwall@jpl-devvax.jpl.nasa.gov (Larry Wall)
Newsgroups: comp.lang.perl
Subject: Re: Crafty automatic file deletion?
Message-ID: <1991Mar29.064752.3833@jpl-devvax.jpl.nasa.gov>
Date: 29 Mar 91 06:47:52 GMT
References: <SQUASH.91Mar15194116@heat.math.ufl.edu> <126507@uunet.UU.NET> <JIK.91Mar28001532@pit-manager.mit.edu> <126658@uunet.UU.NET> <COMPOSER.91Mar28231915@chem.bu.edu>
Reply-To: lwall@jpl-devvax.JPL.NASA.GOV (Larry Wall)
Organization: Jet Propulsion Laboratory, Pasadena, CA
Lines: 18

In article <COMPOSER.91Mar28231915@chem.bu.edu> composer@chem.bu.edu writes:
: It looks like the current filename is in $name.  There may be a place
: where Larry left a $_ and meant $name in the code; but it also probably
: doesn't make a difference in that case.  I'll have to look at it a little
: more closely to make sure; I've only had time to glance at it.

$name = "$dir/$_";

The current basename is purposefully left in $_ so that -name tests can
match against it easily.

And yes, I put some effort into making the output readable, since one
of the primary reasons for using find2perl is when you want to take
find's semantics as a base and then start customizing the script.  s2p,
a2p and find2perl are all intended to be translators, not just compilers.
Code migration is really the primary issue.  That, and brain migration.

Larry