From:	Joshua Juran	Date:	Sat Jul  7 19:15:26 2007
Subject:	Re: [MacPerl] passing arguments: AppleScript to MacPerl

On Jul 7, 2007, at 10:43 AM, Louis Pouzin wrote:

> On Fri, 29 Jun 2007 23:14:37 -0700, Joshua Juran wrote:
>
> set names to {...}
> set argv to names
> copy dog to beginning of argv
> tell perl to do script argv
>
> Hi Josh,
>
> Thanks for your answer. As you can read in my response to Nobumi,  
> this scheme fails on both my mac's. I suspect it is an AppleScript  
> problem, not a MacPerl one.

I verified the contents of argv in OS X's Script Editor.  Obviously,  
you still have to set perl to application "MacPerl", and it's Do  
Script handler has to accept a list, which I didn't check, since it  
seemed to be assumed in the original post.

>> These days I don't use MacPerl anymore -- I have my own port of  
>> perl to a Unix-like environment that runs on classic Mac OS.
>
> Why ? Is this more effective than running OS X ?

On old Macs, you can't run an acceptably recent version of OS X, if  
you can run it at all.  If you can, the performance is awful.  I have  
an OldWorld G3 tower monitoring the modem port and logging incoming  
calls via a Perl script.

If you have a processor-intensive non-Carbon app, it runs much better  
in native OS 9 than in Classic.  My example is ToolServer, for  
running the Metrowerks developer tools.

And it's definitely more effective to run perl in a stdio environment  
than not.  :-)

Josh