On Nov 5, 2005, at 9:48, Tomo wrote:
The usage is following:
1. The parent interpreter creates child a ParrotInterpreter object.
2. The parent interpreter runs the child interpreter with runinterp
opcode.
3. The child interpreter suspends by itself with suspend opcode.
4. The parent interpre
Hello.
>> I enjoy Parrot and tried to write new two opcodes -- suspend and resume.
>> suspend opcode is to halt interpreter and resume opcode is to restart
>> interpreter from where it suspended.
> Hmm. How does the C opcode execute, when the runloop was left?
> No test case there. What would be t
On Fri, Nov 04, 2005 at 11:02:42AM -0500, Will Coleda wrote:
> The mail list strips out .t attachments (Robert? is this necessary?)
This was changed on perl5-porters a few weeks ago, and since then I
don't recall seeming a marked increase in troff spam.
--
Paul Johnson - [EMAIL PROTECTED]
http:
>Please refer to attached souce and test case.
Sorry, I miss test case -- attached.
No, it isn't. =)
The mail list strips out .t attachments (Robert? is this necessary?)
Please follow the instructions at http://www.parrotcode.org/
patchfaq.html, or inline the file to the list.
Thanks.
On Nov 4, 2005, at 8:36 AM, Tomo wrote:
Please refer to attached souce and test case.
.t files seem to be routinely stripped when sending to the list.
If you follow: http://www.parrotcode.org/patchfaq.html, then the
files still won't make it to the list, but they *will* be added to
the generated ticket.
Regards.
On Nov 4, 2005, at 8:58 AM, Leopold Toetsch wrote:
Tomo wro
Tomo wrote:
Hello,
I enjoy Parrot and tried to write new two opcodes -- suspend and resume.
suspend opcode is to halt interpreter and resume opcode is to restart
interpreter from where it suspended.
Hmm. How does the C opcode execute, when the runloop was left?
Please refer to attached souce
