Re: [MacPerl-Porters] What can MacPerl bring to Mac OS X (Server)?

["Jefferson R. Lowrey" <lowrey@mailbag.com>]

At 9:32 PM +0100 2/24/00, Matthias Neeracher wrote:
<snip>
> - There are no Cocoa, Carbon, or BSD command lines to "run under" as such.
>   Any process can pretty much mix & match whatever it wants from Carbon &
>   Cocoa.
> - Specifically, last year I ported some of the MacOS Toolbox modules as
>   dynamic libraries on MacOS X with Carbon and ran them WITH THE STANDARD
>   BSD-style perl version shipping with MacOS X. This worked quite well
>   (considering my total inexperience at the time).

Do you have any notes you can make available from this experiment?  My
feeling is that this is something that the rest of us can be working on
whilst you're busy with MacOS Perl.  This would be a good track for
parallel development, I think.  We can leave the hairier bits of cleaning
up the build process and whatnot to you, and when you get that done - all
the work we've done falls into place.  And work on porting the Classic
MacOs modules can incorporate Cocoa improvements/replacements.

Or am I missing something important?

> - I'm not entirely sure if you can make a #! script into a double clickable
>   application on MacOS X, but if not, it certainly would not require much
>   wrapping effort.

Something can probably be done with packages in this regard, I'd guess.

-Jeff Lowrey



==== Want to unsubscribe from this list?
==== Send mail with body "unsubscribe" to macperl-porters-request@macperl.org