Milscvaer writes: > Running the old Perl5 interpretor and the Parrot in the same process > is not a great solution, since this would mean that there would be two > completely seperate interpretor codebases to support. A big part of > Parrot is to allow several languages to use the same interpretor, thus > allowing them all to benefit from the same solid foundation. It would > be quite ridiculous if Perl did not completely support a past version > of itself on Parrot given we are writing parsers for numerous other > languages for Parrot (a good idea, indeed, but lets make sure Perl5 > has a Parrot parser too).
All your wishes up to this point in the message will come true[1]. That's what Ponie is designed to do. But the first sentence of this paragraph is a little unsettling. Ponie runs most of the Perl 5 interpreter in Parrot (it does use as much of Parrot as it can), but I would still say that it is its own interpreter. It's simply not possible to run on interpreter B when all the code thinks your running in A. It's possible some of the time, but in the general case it is not. So ponie will be most of Perl 5 running in the same process as parrot. And that's just the way it is, and there's no way around it[2]. Luke [1] If you replace every time you said "all" with 97%. Yeah, I know your code depends on all the quirks of Perl 5, etc., etc., but you just can't get them all. Modules that involve perl source patches simply won't work. But then again, those weren't really "modules", were they? [2] Unless you find a way around it and tell us.
