Fred -
Thanks for the help. Now I can see the errors that the script is
generating, but I'm still not sure how to access argv from my perl
script. For example, if I want to assign the contents of argv to
@some_array how do I do that?
Tantalizingly, if i just write:
<code>
#!/usr/bin/perl -w
use strict;
open LOG, ">log.txt" or die "can't open the logfile $!";
foreach my $file (@ARGV) {
print LOG "$file\n";
}
</code>
then I get (just) one of the files, but this leads me to believe that
I don't need to create my own array. Any help is appreciated.
Thanks!
--Josh
> File names are passed via argv[]. I would suggest that you
>monitor the console log (run Console.app) while creating the droplet
>and see if there are any errors, and if none do the same while
>dropping files on the new droplet. Error reporting via the UI is
>nonexistant. Perhaps it's failing to set the executable bit on the
>script placed in the droplet or something.
>
> -Fred
>
>On Friday, November 30, 2001, at 11:43 AM, Joshua Kaufman wrote:
>
>>How are the names of the dropped files passed to the script? For
>>example, when I make the following script into a 'droplet' it
>>silently fails to even create the log file. Are the file names not
>>passed to @ARGV? are there permissions issues?
--
