Re: [MacPerl] Perl Shared Library (was Re: [MacPerl] ports and builds)

[Matthias Neeracher <neeri@iis.ee.ethz.ch>]

In article <online-1401992020110001@108-ppp-its.caltech.edu>, online@mactech.com (Jeff at MacTech) writes:

> In article <mac-perl.86d84i8sdw.fsf@gwaihir.ee.ethz.ch>, Matthias
> Neeracher <neeri@iis.ee.ethz.ch> wrote:
>> While I do agree with the basic feeling that Perl should be available in a more
>> embeddable form and actually am working (slowly) toward that goal, the actual
>> distribution logistics are going to be difficult.

> I've been thinking about this for a while. This may already be what you
> have in mind, but just in case, a few comments:

> Under Unix and Win, the Perl app itself tends to be tiny

Not so, at least not on those Unix systems I know.

> 1) Multiple Perl apps could run simultaneously without (or independent of)
> threading in the interpreter. They would each have a large memory
> footprint, but a small disk footprint which would be ideal for
> distribution. 

- Other things being equal, multithreading is usually more efficient than
  multitasking on the Mac.
- Large memory footprints are bad.
- I'll grant you the theoretical advantage of the small disk footprint. In
  practice, I'm unable to name a single Mac system where distributing small
  programs linked against a large shared library has really taken off. Even
  Java, which has enormous amounts of engineering talent and API stability
  invested, is not excactly flooding the PD archives.

> 2) Also, as is the standard argument, updated version of the shared lib
> would automatically benefit all of these apps. 

Or break them, respectively :-)

> 3) More importantly, though, is this: writing a "real" Mac app (ie, a
> Toolbox-heavy app) presently involves a lot of shenanigans which are the
> result of living within the MacPerl app

I see the relationship as being a quite successful symbiosis: In my own
scripts, I find it very convenient being able to write just a small bit of code
resting inside a substantial application.

>>> 2) Perl libraries (/usr/local/lib/perl5/*) should be placed relative to 
>>> this shared library
>> 
>> What I've experimented with is a symbolic link in the perferences folder.
>> I prefer not to install major directory trees in the system folder

> Isn't there now an "Application Support" folder in the System Folder? This
> seems like the appropriate place for things, with the possible option of
> putting an alias here instead of the actual hierarchy.

Good idea.

>> In particular, I would be interested in finding out how Perl is
>> going to fit into MacOS X (my understanding is that it's shipping in MacOS X
>> Server, would you happen to know who is responsible for that port?).

> Hopefully you'll get the full scoop, but my guess is that the version in
> MOSXS is minimally changed from the standard Unix perl.

True, at least for MacOS X server.

Matthias

-- 
Matthias Neeracher   <neeri@iis.ee.ethz.ch>   http://www.iis.ee.ethz.ch/~neeri
   "I'm set free to find a new illusion" -- Velvet Underground

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