There are basically 3 sane ways to do P5/Rakudo interop:
- let Rakudo parse Perl5 (-> v5)
- call into libperl via Rakudo's C FFI (-> Inline::Perl5)
- properly integrate the Perl5 object system into 6model (-> diakopter's grant)
All of these approaches have their pros and cons.
| [reply] [Watch: Dir/Any] |
There are basically 3 sane ways to do P5/Rakudo interop:
Given:
- all the years put into libperl;
- plus the fact that it is a moving target;
- and that it is known to be, as near as makes no difference, impossible to emulate all its functionality, quirks and bugs with any degree of accuracy
I'd say that there is only one sane way to do P5/Rakudo interop, and that's your option 2.
Which as I read it, is what the OP is announcing.
With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'
Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.
| [reply] [Watch: Dir/Any] |
Very "helpful" attitude you show here. You seem to have appointed yourself to be "the crusader against helping Perl6 move along". Please do us all a favour and go away.
CountZero A program should be light and agile, its subroutines connected like a string of pearls. The spirit and intent of the program should be retained throughout. There should be neither too little or too much, neither needless loops nor useless variables, neither lack of structure nor overwhelming rigidity." - The Tao of Programming, 4.1 - Geoffrey James My blog: Imperial Deltronics
| [reply] [Watch: Dir/Any] |
| [reply] [Watch: Dir/Any] |
| [reply] [Watch: Dir/Any] |