Path: utzoo!attcan!uunet!know!sdd.hp.com!zaphod.mps.ohio-state.edu!julius.cs.uiuc.edu!apple!olivea!orc!inews!cmdnfs!bhoughto
From: bhoughto@cmdnfs.intel.com (Blair P. Houghton)
Newsgroups: comp.lang.perl
Subject: Re: PERL compiler ?!?
Message-ID: <968@inews.intel.com>
Date: 14 Nov 90 19:35:06 GMT
References: <MITCH.90Nov9124943@hq.af.mil> <1990Nov13.100359.1846@squirrel.mh.nl> <1990Nov14.105212.11777@robobar.co.uk>
Sender: news@inews.intel.com
Organization: Intel Corp, Chandler, AZ
Lines: 20

In article <1990Nov14.105212.11777@robobar.co.uk> ronald@robobar.co.uk (Ronald S H Khoo) writes:
>Johan Vromans <jv@mh.nl> writes:
>> Somehow it must be possible to save the internal code of a compiled
>> program in a (possibly) system (and PERL?) independent format.
>
>This would be very nice.  Yes please. :-)  Then we can rewrite all of
>/usr/bin and /bin in perl, and save a *lot* of disc space.

Ever thought of layered run-time libraries?

I bet perl scripts would cook kittens in compiled form
under VAX/VMS.

(Of course, this is manifestly the machine-code
incarnation of interpreters, but it saves on the
context switches. :)

				--Blair
				  "RTL: The only thing that
				   makes VMS non-valueless."