Ponie: Perl On New Internal Engine 47
caseywest writes "Today at his State of the Onion speech during the 2003 O'Reilly Open Source Convention, Larry Wall announced the Ponie project (somewhere within his legendary humorous presentation). Ponie involves rewriting central parts of the Perl 5 interpreter to run on Parrot, the Perl 6 virtual machine, including a C API emulation layer to make existing XS code work. Arthur 'sky' Bergman is sponsored by his employer Fotango to develop Ponie. Currently, a press release and a FAQ are available. More details will be available in due time."
Scheme (Score:2, Interesting)
Also Dan said that Parrot is more suitable for dynamically typed languages like those, while Mono and dot net are better for statically typed, like C# and Java. Anyone know more about that?
Re:Scheme (Score:3, Interesting)
A system that combined some of the semantics of Lua with Scheme would actually be the most suited to this type of task. If you don't know what Lua is, well, it has hooks that allow you to specify events which occur when certain things happen. Like, when a hash table is accessed, you can overload that behavior (which Perl has with TIE), or when an undefined subroutine might be called, you can override that behavior. (which Perl has with AUTOLOAD). Lua 5 just got coroutines, lexical closures, and tail calls - sounds an *awful* lot like Scheme, no?
-toomuchPerl
Re:Scheme (Score:2, Interesting)
So
Re:$perl %syntax @sucks (Score:4, Interesting)
In any case, the concerns about context are completely baseless. So what? It's not like context is subjective in Perl. It's just a factor to deal with when programming. It makes the code more expressive with less effort. That's one of the stated goals of Perl: laziness. In this case, it's a great idea. Not one that is perfectly implemented in Perl, necessarily, but nonetheless a fantastic notion.
Re:Scheme (Score:3, Interesting)
Re:Scheme (Score:2, Interesting)
Whether or not my perspective is wrong, my view is this:
Also, to reiterate, I'm not saying a pure Scheme interpreter. But the semantic model of Scheme matches all these languages very closely, and there are a good number of Scheme bytecode-based interpreters available. It makes sense to not only support Scheme, but to also seriously consider it from a design standpoint.
Why is Scheme viewed as the ugly cousin, with Perl, Ruby, and Python ganging up? And more importantly, why do Ruby and Python communities look down so snobbishly upon Perl?