On Tuesday 01 August 2006 02:52, Leopold Toetsch wrote:
> Two things come to my mind:
> 1) why is it creating 2 interpreters?
Per my experiments, this worked out the best. That is, if there's an error in
the compiled code, reusing an interpreter gave weird answers. I haven't
tracked this down
Am Dienstag, 1. August 2006 07:20 schrieb chromatic:
> Hi all,
>
> Here's a patch for discussion.
Two things come to my mind:
1) why is it creating 2 interpreters? What is the $parent used for?
And related: is $interp ever cleaned up by calling Parrot_exit()?
2) This looks a bit bogus (there
Hi all,
Here's a patch for discussion. It adds a new test module that uses a Parrot
embedded in Perl 5 to run pir_output_*() tests. It's a bit fragile and
depends on Embed::Parrot (which I haven't checked in yet). I'm just posting
it here to document that it exists and works in some cases, a
