Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!samsung!emory!gatech!bloom-beacon!eru!hagbard!sunic!mcsun!hp4nl!mhres!squirrel!jv From: jv@mh.nl (Johan Vromans) Newsgroups: comp.lang.perl Subject: Re: PERL compiler ?!? Message-ID: <1990Nov13.100359.1846@squirrel.mh.nl> Date: 13 Nov 90 10:03:59 GMT References: Sender: jv@squirrel.mh.nl (Johan Vromans) Reply-To: Johan Vromans Organization: Multihouse Automation, the Netherlands Lines: 24 In-Reply-To: mitch@hq.af.mil's message of 9 Nov 90 17:49:43 GMT In article mitch@hq.af.mil (Mitch Wright) writes: > Has anyone ever considered writing a PERL compiler? With regard to the nature of PERL: the generated binary would need to include the whole PERL compiler itself. This eliminates one of the most obvious advantages of compilation: a small binary. However, a means to save the compiled PERL program in a (sort of) executable file, and have PERL execute it, would be very handy. It eliminates the need for parsing, translating and compilation upon every invokation. No, I do not consider undumping a good alternative for this, since it produces huge binaries and it makes it impossible to execute existing binaries with a new interpreter. Somehow it must be possible to save the internal code of a compiled program in a (possibly) system (and PERL?) independent format. And, of course, autoloading... Johan -- Johan Vromans jv@mh.nl via internet backbones Multihouse Automatisering bv uucp: ..!{uunet,hp4nl}!mh.nl!jv Doesburgweg 7, 2803 PL Gouda, The Netherlands phone/fax: +31 1820 62911/62500 ------------------------ "Arms are made for hugging" -------------------------