Re: [MacPerl-Porters] perl shared library request (or job offer)

[Robert Dye <rob.dye@ni.com>]

on 2000.02.22 9:54 AM, Chris Nandor at pudge@pobox.com wrote:

> At 8.43 -0700 2000.02.22, Kevin Walker wrote:
>> I'd like to embed the basic perl interpreter (not necessarily
>> including any of the mac-specific aspects of macperl) inside another
>> application -- actually, inside a plug-in module I'm writing for
>> another application.

We also would like to do this for our app. Last summer I had an intern work
on this and he found it quite easy to do on the Windows and Unix platforms
because the standard distributions include dlls that you can link to.

>> I looked into trying to build such a shared lib myself from the perl
>> source code, but found the task daunting.

I'm in complete sympathy here. Both my intern and I were amazed at the
arcane and complex build process for MacPerl. Is there a chance that the
build process will be simplified in the next rev? If I recall correctly,
there were also some dependencies upon an obsolete CodeWarrior 11 library,
and specific versions of other libraries. Will these dependencies go away?

Of course, these worries are only academic if the following comes true:

> This beast may exist sometime "soon."  A port of MacPerl to the 5.6 source
> (which is in beta now for Unix and Windows) is in progress, and may include
> a shared library.  So my suggestion is to wait.  Matthias Neeracher is the
> guy doing the work, and he is on this list.

I'd like to voice my whole-hearted and enthusiastic support for this effort!
Please make the "may exist" be a "will exist"!

BTW, if the shared library effort works out, I'd like to put in a feature
request:

Make it possible to trap "exit" and "die" so that a perl plugin does not
bring down the entire app when a script decides to execute one of these
commands.



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