Re^8: v5, a reimplementation of P5 (was Re^5: A "Perl-7" that I could actually USE right now)

in reply to Re^7: v5, a reimplementation of P5 (was Re^5: A "Perl-7" that I could actually USE right now)
in thread A "Perl-7" that I could actually USE right now

lend me some of your dust ...

Comment on Re^8: v5, a reimplementation of P5 (was Re^5: A "Perl-7" that I could actually USE right now)

Replies are listed 'Best First'.
Re^9: v5, a reimplementation of P5 (was Re^5: A "Perl-7" that I could actually USE right now) by chromatic (Archbishop) on Jul 10, 2013 at 23:26 UTC
Oh, I already wrote code to handle the sharing of entities between Parrot-hosted languages and Perl 5 (the hard part was walking between the two very different memory management strategies of garbage collection and reference counting). I'm sure that code's been lost to one of the annual purges, however. I have no desire to rewrite working code for the sake of P6's current implementation fad—but good luck doing that in a cross-platform way in NQP, or handling internal encoding and decoding in an efficient way, or dealing with system calls, or managing library paths, for example.	[reply]

Replies are listed 'Best First'.

Re^9: v5, a reimplementation of P5 (was Re^5: A "Perl-7" that I could actually USE right now)
by chromatic (Archbishop) on Jul 10, 2013 at 23:26 UTC

Oh, I already wrote code to handle the sharing of entities between Parrot-hosted languages and Perl 5 (the hard part was walking between the two very different memory management strategies of garbage collection and reference counting). I'm sure that code's been lost to one of the annual purges, however. I have no desire to rewrite working code for the sake of P6's current implementation fad—but good luck doing that in a cross-platform way in NQP, or handling internal encoding and decoding in an efficient way, or dealing with system calls, or managing library paths, for example.

[reply]

In Section Meditations