Well, thanks for asking, I'm sure it would be interesting to talk about this stuff but I won't be there. Best of luck on your ANTLR work and ASM work. Im still wondering myself what could be gained by using ASM.On 4/29/07, Charlie Groves <firstname.lastname@example.org > wrote:On 4/28/07, Leo User <email@example.com> wrote:
> I believe there are implementations of all language changes from 2.3 to 2.5
> on svn. Yield as an expression is still in progress, really that's just a
> question of finding places where using it as an expression is going to cause
> problems. For the most part classical byte code output is ok. When its not
> ok is say when a new object is being constructed and you have a yield
> expression as one of the parameters. Then something different has to
> happen. Im planning on doing 2.6 features as soon as they are finalized by
> the python PEP for 2.6. Maybe something like switch statements will show up
> once its put together.
This should be of interest to the summer of code crew working on
improving the compiler and getting to 2.5 language level support.
Since they're replacing the parser with ANTLR and CodeCompiler.java
with asm it won't be directly applicable, but at least the way the
newer language features hook into the runtime should be similar.
I am part of that crew, and can nothing but agree with Charlie, there are definitely some interesting features in JythonX. I checked out the source from svn about two weeks ago, and started looking at it. I haven't had that much time though, since I am still up to my ears in my courses for this semester.
In about a week from now I will be in San Francisco for JavaOne and it would be great to meet as many of you guys as possible there to discuss various ideas. If I remember correctly you were supposed to be there Leo, weren't you? I would very much like to meet you there to get input from your experience from JythonX.