Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!qt.cs.utexas.edu!cs.utexas.edu!uunet!mcsun!hp4nl!mhres!squirrel!pronto!jv From: jv@mh.nl (Johan Vromans) Newsgroups: comp.lang.perl Subject: Re: Ruminations on the future of Perl Message-ID: <1991Jun29.092309.1776@pronto.mh.nl> Date: 29 Jun 91 09:23:09 GMT References: <2gaH&?b#@cs.psu.edu> Sender: jv@pronto.mh.nl (Johan Vromans) Reply-To: Johan Vromans Organization: Multihouse Automation, the Netherlands Lines: 16 In-Reply-To: flee@cs.psu.edu's message of 28 Jun 91 20:53:38 GMT X-Md4-Signature: 5e4cbc86cc3b3aefd8c302a84f070f23 In article <2gaH&?b#@cs.psu.edu> flee@cs.psu.edu (Felix Lee) writes: Perhaps I should clarify. What I have is pieces of a Perl parser. Once that's done, the obvious next step is a semantic analysis and optimization phase. And then a code generator can generate whatever sort of back-end code you like: assembler, C, Scheme, whatever. Scheme seems to me to have several advantages over C. How about a perl front-end for gcc? 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" -------------------------