RFC: Move build tools to Perl5, developer tools to Perl6

Vasily Chekalkin bacek at bacek.com
Fri Feb 22 12:26:08 UTC 2013


"At the end of the days" bytecode shouldn't be "written in text format"
(e.g. PIR). Generating bytecode from within code without textual
representaion is way to go. So, winxed/nqp/whatever should not generate
"assembly code" (which is PASM/PIR) and all this discussion is mostly
irrelevant for future.


On Fri, Feb 22, 2013 at 3:50 PM, Jonathan "Duke" Leto <jonathan at leto.net>wrote:

> Howdy,
> I'm saying theese because I couldn't see what benefit for the end user is. And what motivation that I could see is to popularize Winxed, which is not parrot should do.
> The benefit to the "end user" is that Winxed allows Parrot developers to
> write parts of Parrot in Winxed, which is infinitely more pleasant than
> PIR, is more maintainable and allows features to be developed more quickly.
> Duke
> --
> Jonathan "Duke" Leto <jonathan at leto.net>
> Leto Labs LLC http://labs.leto.net
> 209.691.DUKE http://dukeleto.pl
> _______________________________________________
> http://lists.parrot.org/mailman/listinfo/parrot-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.parrot.org/pipermail/parrot-dev/attachments/20130222/d755bb18/attachment.html>

More information about the parrot-dev mailing list