Marcus Petersson:
# I wonder if it's possible to add your own custom opcodes yet.
# What I have
# in mind are ops for about 10 external functions. AFAIK, there
For now, just add the desired ops to core.ops and rebuild Parrot; make
should Do The Right Thing. In the future it will be more complicated so
it can support oplibs loaded at runtime and such.
# Btw, wouldn't it be good to set up a parrot-user ML soon? And
Right now, Parrot is an alpha program. 'Nuff said.
# shouldn't
# this list rather be called parrot-dev? I imagine that once
# implementation
# of Perl6 starts, it will otherwise be swamped with
# Perl-specific issues.
# Personally, I have no interest in Perl, quite little in the
# actual Parrot
# implementation, but very much in using it for other purposes.
First and foremost, Parrot is Perl 6's runtime. We're just trying to
design it in such a way that other languages can utilize it without
jumping through too many hoops. Besides, the 'Perl-specific issues'
are:
a) very far off (we don't even have most of the language spec yet), and
b) good examples of how to make Parrot work with an actual HLL.
--Brent Dax
[EMAIL PROTECTED]
Configure pumpking for Perl 6
"Nothing important happened today."
--George III of England's diary entry for 4-Jul-1776
