Re: Re: Favorite Perl 6 feature?

[zby]

That's pretty much like me. In the regexp I like that 'closure' property - that you can call code from regexp and the other way. And as for cute operators I like the vector operators. For the last point about Parrot - well Perl libraries are I think the bigest so I believe it will be much more the other way around - ruby/python/brainfuck programmers using Perl libraries.

[diotalevi]

Regexps are already closures via the ??{ construct. You just can't jump back into regexp because the engine isn't re-entrant (though I hear it works a bit - I seem to fall over all the nasty bits). What I'm really pining for are:

• Grammars for binary data (P::RD chokes)
• Being able to locally redefine the language
• Getting full access to the VM and in a meaningful way since perl5's VM is so clunky to work with
• Junctions!
• Lazy pipelining
• Co-routines

And I want these not because they're cool but because at various points I could have made my own code simpler, more efficient or had some otherwise significant improvement.

[demerphq]

Grammars for binary data (P::RD chokes)

I guess preprocessing the input into strings of 1s and 0s isn't (?x: fast | efficient | good ) enough? (Should get around the choke no?)

;-)


---
demerphq

_{<Elian> And I do take a kind of perverse pleasure in having an OO assembly language...}

[diotalevi]

[Added Its been brought to my attention that the link doesn't work. It does but you have to change the "search in" select widget from "Modules" to "All". The CPAN librarian didn't think this was a good name for the module so the name didn't get registered and it can't be linked to easily. I may just rename it to "Xerox::Metacode::Reader" but I was trying to avoid having a company name as a root level category in CPAN. Oh well. If you've got an opinions regarding the module and its name I'm interested.]

That didn't even occur to me. Oh well - that wouldn't have been fast enough anyway. The final results ended up in Metacode::Reader.