Java continuations (was: with joeq)

[Torsten Curdt <tc...@vafer.org>]

> My opinion: probably not. However, I just thought of another drawback 
> with using Joeq's interpreter, namely you wouldn't be able to debug it 
> with a standard Java debugger. The Brakes-like approach doesn't have 
> this limitation. In addition, since that approach simply modifies the 
> bytecode it would still be optimized by Hotspot and would still 
> outperform any scripting language. Torsten, what's the status of your 
> work on this?

Since my proof-of-concept nothing much happend regarding the code.
I prepared a block that is sitting on my disk.

I talked to the brakes guys and was supposed to get an official
"go" around christmas. I haven't heard anything yet and have to
admit I did not press on this anymore. Maybe it's not even necessary
but I'd prefer to be save on such legal aspects.

I also talked to James Strachan and the guy from RIFE. We thought
it would be a good idea to share the efforts and create general
java continuations project until java might get native continuations.
We could also (at least) try to push this a little. But this also
stalled probably due to the lack of time.

Although quite some people contacted me in private on this subject
I thought we (cocoon) decided to go the javascript way and not create
too many options in this area.

...but java continuations with the compiling classloader sounds
pretty cool to me :)

Do you guys want me to push this a little more again?

cheers
--
Torsten

Re: Java continuations

[Stefano Mazzocchi <st...@apache.org>]

Torsten Curdt wrote:

> ...but java continuations with the compiling classloader sounds
> pretty cool to me :)

I agree. I would also like to try out Groovy or Jython...  but I do have 
fears on diverging too much.

I mean: do you guys think we really got the point where we understand 
what we want to do with continuations?

> Do you guys want me to push this a little more again?

I would like to have a discussion on where do we stand "research-wise" 
on the flow with continuations concept, before trying to attach "what 
syntax should we use".

I mean, it would be totally cool if we had

  - javascript
  - java
  - groovy
  - python

and then, just like we did with Woody, we would standardize on one.

But I still feel this is too early to do, I mean, we already have to 
sell the concept and we don't want to spoil our own marketing by 
early-diversifying that much.

This said, I see nothing wrong in starting a "continuations for java" 
project, say under jakarta, that would glue together people from cocoon 
and groovy (potentially rhino and jython too!).

This can totally happen in parallel.

And, if anything comes out, put it in the scratchpad for people to try out.

I mean, stabilizing is good, but we don't want to stop innovating either ;-)

In media stat virtus.

-- 
Stefano.