Tim Bunce:
# On Fri, Mar 01, 2002 at 05:17:28AM -0800, Brent Dax wrote:
# > After banging my head against a wall for a few hours with
# Perl 5's XS, I
# > have an idea for how Parrot can do it better.
#
# I'm not sure about Parrot, but for Perl 6 Larry has specifically
# said that he intends to extend to Perl "sub" declarations to enable
# them to contain all the information required to link to external
# libraries.
Coo. I haven't heard that, but I'm sure there's much I haven't heard.
:^)
# But that might have to wait for Apocalypse 21.
I'll just be happy to see Apoc 5, so I know what I should support when I
rip out the guts of the regex engine. ;^)
# Also, on a tangent, I hope someone is pondering, or planning to
# ponder, the practicallity of some kind of perl5 XS to perl6 interface
# that would enable perl5 extensions to be ported to perl6 with less
# effort than a complete rewrite. It needn't be clean, elegant, or
# fast, but I think there's too much good work on CPAN to ignore.
Unfortunately, Parrot has a very different architecture. If you're
directly manipulating the stack, it's going to be impossible to emulate
and almost as hard to machine translate. Same if you're mucking around
in SV internals or doing all sorts of other crap. The simple stuff,
however, should be easy to machine-translate to whatever format XS6
uses.
--Brent Dax
[EMAIL PROTECTED]
Parrot Configure pumpking, regex hacker, embedding coder, and boy genius
#define private public
--Spotted in a C++ program just before a #include
