Er, @ARGV, that is. -C
At 8:43 AM -0600 9/5/2002, Charles Albrecht wrote: >More to the point, > > %ARGV > >-Charles > [EMAIL PROTECTED] > > >At 1:42 PM +0000 9/5/2002, [EMAIL PROTECTED] wrote: >>Well, you might call a script like this: >> >> >perl foo.pl file1 file2 file3 >> >>where each argument to the script (in this case 3 files) is passed in >>to the script, separated by a space. >> >>If I created a DropScript out of my foo.pl, and dropped file1, file2, >>and file3 onto it, it would be just like typing the command above. >> >> >>Pete >> >>On Thu, 05 Sep 2002 20:37:20 +1000, "Shannon Murdoch" >><[EMAIL PROTECTED]> said: >>> Hi Pete, >>> >>> Unfortunately I'm not a command-line wiz <:(. Could you explain how >>> the >>> target file/directory parameters are usually passed to the script when >>> it IS >>> called from the command line? >>> >>> Cheers, >>> -Shannon >>> >>> >>> On 5/9/02 2:59 AM, in article >>> [EMAIL PROTECTED], >>> "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote: >>> >>> > These are the notes I had on DropScript from April 23, 2002: >>> > >>> > In the old version of DropScript, it would run the script once for each >>> > file dropped on it. Now it takes all of the files dropped on it, and >>> > passes the list to DropScript, which is the way MacPerl droplets do it, >>> > or the way the command line does it... >>> > >>> > http://www.mit.edu/people/wsanchez/software/ >>> > >>> > I'm thinking it should take whatever you drop on it (file or folder) >>> > and pass it in just as if you called the script from the command >>> > line... >>> >>> >> >> >> >>-- >>http://fastmail.fm/ - Consolidate POP email and Hotmail in one place
