On Wed, Sep 04, 2002 at 10:27:42PM -0400, Melvin Smith wrote:
>This is no surprise. Parrot documentation will be lacking until
>things settle down.
Actually it's not so much the documentation. I didn't complain about
0.0.7 and 0.0.8 requiring changes to parrot-gen.py, because that's
simply to be
[Please CC: me on any responses.]
I follow the perl6-internals list through checking the archive, and
noticed Jerome's posting. I wrote the parrot-gen.py script that he
pointed to. Here are my comments on this issue.
(Note that I do not speak for the python-dev gang as a whole, but
AFAIK I'm
I'd like to resume working on the Python->Parrot translator, and am
wondering where to put the PMCs I'll have to write. I'm reluctant to
add them to classes/, because that's not going to scale. So, how are
future Parrot-based languages going to be distributed?
A fairly simple way might be to
