RFC: Move build tools to Perl5, developer tools to Perl6
gerd.r.devel at googlemail.com
Fri Feb 15 17:10:36 UTC 2013
> I still plan on supporting conversion of .ops to .c without
> having to have anything other than current parrot deps installed (e.g. perl5
> is fair game, but not perl6).
Why is Perl6 not fair game? We're talking about stuff that used to
have no runtime dependencies on the particular Parrot build - reading
in some text files and spitting out some more text files
(nci_thunk_gen.pir does some nasty things with dlfunc and the
Parrot_dt_*() functions right now, but that should be fixed).
It could be implemented in Python or whatever other language floats
your boat. So why not Perl6 where it makes sence (ie as the natural
upgrade path from NQP-rx). Keep in mind that building an unmodified
Parrot would not depend on Perl6 being present.
More information about the parrot-dev