Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!yale!cmcl2!kramden.acf.nyu.edu!brnstnd
From: brnstnd@kramden.acf.nyu.edu (Dan Bernstein)
Newsgroups: comp.lang.perl
Subject: Re: can we ever compile perl?
Message-ID: <15591:Dec1323:30:2490@kramden.acf.nyu.edu>
Date: 13 Dec 90 23:30:24 GMT
References: <110306@convex.convex.com> <1990Dec13.034336.21769@usenet@scion.CS.ORST.EDU> <93725765@bfmny0.BFM.COM>
Organization: IR
Lines: 17

In article <93725765@bfmny0.BFM.COM> tneff@bfmny0.BFM.COM (Tom Neff) writes:
>  2. For many of us, it would be enough to be able to make fast-loadable
>     "Perl object files," i.e., write all data structures to disk after
>     compilation & before execution.

Supposedly perl -u does that, but it doesn't work on many systems. As an
alternative I might suggest that you try to work my pmckpt checkpointer
into Perl. pmckpt 0.95 (which I just made available for anonymous ftp
from stealth.acf.nyu.edu) has been reported to work on (gasp) System V
machines, as well as my native environment. Both Larry and Tom seemed
slightly interested in the code a few weeks ago, but appear to have
abandoned it (sigh).

The reason pmckpt is so portable, btw, is that it doesn't use setjmp()
or longjmp(). Guess what it uses instead...

---Dan