[MacPerl] B. (was re: Distributing reduced MacPerl package with Droplet ?)

[Lionel Artom-Ginzburg <lionel@bigtime.blank.org>]

>At 06.14 98.02.02, Toni Zollikofer wrote:
>>I while ago, found out (with some hints from Chris Nandor) that Droplets or
>>runtime modules do not work without the MacPerl package, if they reference
>>libraries or modules (with "use" or "require").
>>At least, I found it impossible to recursively paste in everything whats
>>called during execution (if there IS a way, please tell me).
>
>Well, actually, droplets will not run AT ALL without the MacPerl
>executable.  Runtimes will run without the executable, but not without
>libaries that it needs.  However, TEXT libraries and modules can be
>embedded in the resource fork of the runtime, so you do not need an extra
>folder.

Which brings me to a separate question-- I realize that it's a 
substantial effort, given the differences between Unix boxes and Macs, 
but has anyone tried porting B, the Perl-to-C converter, to the Mac?  
Will it perhaps work with some slight modifications under MPW?  (I don't 
know much about MPW C, but obviously you'd have to rewrite the makefile 
directives)  Is it hidden in a deep directory of the MacPerl installation 
that I haven't yet found and thus I'm asking a stupid question?  Is this 
the stated purpose of the "save Runtime" option? There are occasions 
where it'd be nice to distribute stuff written in MacPerl in a single, 
executable binary form  (With source code included, of course, in 
accordance to the Artistic License).  For instance, I have a couple of 
Perl scripts which I'd like to run at system boot-up, but given the extra 
time it takes to launch MacPerl from startup, it's inconvenient.  These 
scripts in particular could be converted to C with maybe a days work 
each, since they don't do anything particularly complicated, but being a 
Perl programmer, I'm Lazy...

Lionel








***** Want to unsubscribe from this list?
***** Send mail with body "unsubscribe" to mac-perl-request@iis.ee.ethz.ch