comment on

parrot is currently too slow to be an efficient competitor, there's not much progress, and there was heavy mismanagement. Feature-wise it is an interesting alternative.

But there is a lot going on.

Larry is already writing a p5 grammer for perl6/nqp, and had with MAD a working src-level translator.
Flavio Glock has with perlito a src level translator and compiler already.

perl6 is quite perl5 compatible, with much more features and better performance than perl5 for complicated use-cases, which you would call "Modern Perl" (i.e. Moose, Grammars, ...). But it is totally post-modern perl.

perl11.org (5+6=11) is an umbrella project to try to mix/replace the various parts, parser, compiler/optimizer, runtime. See irc.perl.org #perl11

I am thinking of an implementation based on vmkit to replace parrot or write a better p5 vm, codename p2.

rakudo is working into similar directions, making nqp on jvm or mono or whatever possible.

Perl5 XS is not that big a deal. Either throw it away as it is inefficient and hard to work with anyway. Or provide convenience wrappers. Better languages provide better glue interfaces. Inline e.g. is much better, but you still have to deal with the XS API.

In reply to Re: Why no one port perl5 to Parrot? by rurban
in thread Why no one port perl5 to Parrot? by xiaoyafeng

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Do you know where your variables are?
	PerlMonks