Re: [perl #22717] [PATCH] take 2: convert parrot to continuation passing style

2003-06-18 Thread Dan Sugalski
At 7:58 PM + 6/16/03, Jonathan Sillito (via RT) wrote: [perl #22633] [PATCH] convert parrot to continuation passing style" is outdated. Attached is a less ambitious patch to convert parrot to continuation passing style. Here is a summary of the ops (recall that the continuation gets stored in P

The start of objects, in object.ops

2003-06-18 Thread Dan Sugalski
I've decided part of the implementation for objects, and started in on the ops for them. Right now it's just a sketch, but the following ops are going in: newclass Px, Sy Creates a new, standalone class named Sy, class PMC put in Px. subclass Px, [SPy], [Sz] Subclass $2, and put the new subcl

ad #22717: CPS and more

2003-06-18 Thread Leopold Toetsch
[my last 2 f'ups didn't arrive at perl.perl6.internals, so I try again] The patch is fine with two exceptions: 1) still breaks existing P6C tests WRT exceptions & rules 2) performance of CPS sucks ad 1) I'd like to preserve the old style invoke/ret scheme too. incokecc and friends could call a new

RE: ad #22717: CPS and more

2003-06-18 Thread Jonathan Sillito
> -Original Message- > From: Leopold Toetsch [mailto:[EMAIL PROTECTED] > > The patch is fine with two exceptions: > 1) still breaks existing P6C tests WRT exceptions & rules > 2) performance of CPS sucks > > ad 1) I'd like to preserve the old style invoke/ret scheme too. incokecc > and frie

Re: ad #22717: CPS and more

2003-06-18 Thread Leopold Toetsch
Jonathan Sillito wrote: -Original Message- From: Leopold Toetsch [mailto:[EMAIL PROTECTED] The patch is fine with two exceptions: 1) still breaks existing P6C tests WRT exceptions & rules You didn't mention this point. It might be only a small change in P6C code, I didn't look at (4 tes

RE: ad #22717: CPS and more

2003-06-18 Thread Jonathan Sillito
> -Original Message- > From: Leopold Toetsch [mailto:[EMAIL PROTECTED] > > Jonathan Sillito wrote: > > >>-Original Message- > >>From: Leopold Toetsch [mailto:[EMAIL PROTECTED] > >> > >>The patch is fine with two exceptions: > >>1) still breaks existing P6C tests WRT exceptions & rul

Re: ad #22717: CPS and more

2003-06-18 Thread Leopold Toetsch
Jonathan Sillito wrote: -Original Message- From: Leopold Toetsch [mailto:[EMAIL PROTECTED] Ok then we need a new opcode: newsub Px, .Class, jump_or_ret_addr Sounds fine to me. At one point the following worked: new Px, .Class, address Extending the C opcode or doing a new one isn'

Re: ad #22717: CPS and more

2003-06-18 Thread Melvin Smith
At 02:34 AM 6/19/2003 +0200, Leopold Toetsch wrote: Jonathan Sillito wrote: (3) One other efficiency thought: I wonder if the interpreter's context could be changed to a pointer to struct Parrot_Context? This would make accessing the stacks slightly slower but would of course make restoring the con

Re: ad #22717: CPS and more

2003-06-18 Thread Dan Sugalski
At 5:07 PM +0200 6/18/03, Leopold Toetsch wrote: [my last 2 f'ups didn't arrive at perl.perl6.internals, so I try again] The patch is fine with two exceptions: 1) still breaks existing P6C tests WRT exceptions & rules Yeah, that needs fixing. 2) performance of CPS sucks Are you sure? Tell us what

Re: ad #22717: CPS and more

2003-06-18 Thread Dan Sugalski
At 10:23 PM -0400 6/18/03, Melvin Smith wrote: At 02:34 AM 6/19/2003 +0200, Leopold Toetsch wrote: Jonathan Sillito wrote: (3) One other efficiency thought: I wonder if the interpreter's context could be changed to a pointer to struct Parrot_Context? This would make accessing the stacks slightly sl