[pypy-dev] is anyone actively hacking on the JVM backend?

[Paul deGrandis]

I'm working on some stuff but it's been stalled for awhile because I
didn't have Java6 on the mac.  That changed yesterday, but I'm dealing
with school.... so have at it!  Let me know if I can help with
anything!

Paul

On 11/29/07, amit <regmi.amit at gmail.com> wrote:
> Hi Niko,
>
> I am working on the "CLR" module --- ..pypy/module/clr/
> Just trying to play around with   "interp_clr.py"  and  "app_clr.py"  in
> there.
> Hope your commits will make it more better.
>
> regards,
> AmitReg
>
>
>
> Maciej Fijalkowski wrote:
> > As noone answers... I think amitReg is doing some CLI related stuff,
> > which means you can stomp on each other on oosupport, but he's doing
> > rather library integration, so sounds very unlikely.  Besides, I'm not
> > aware of anyone.
> >
> > Cheers,
> > fija
> >
> > On Nov 29, 2007 7:46 PM, Niko Matsakis <niko at alum.mit.edu
> > <mailto:niko at alum.mit.edu>> wrote:
> >
> >     I have been making small improvements to the JVM backend: I am aiming
> >     towards eliminating any remaining conformance problems, and also
> >     towards fixing a few warts in the implementation.
> >
> >     Right now I am wringing out the last few bugs from a check-in that
> >     would allow multiple PyPy-generated interpreters to be used
> >     simultaneously.  Currently, the code uses a few static fields that
> >     would conflict if, for example, someone tried to load both a Python
> >     and a Smalltalk interpreter into the same JVM.  These static fields
> >     were used to allow the helper code (src/PyPy.java and friends) to
> >     create instances of exception classes and other RPython-generated
> >     code.  The new code creates a single instance of the PyPy helper class
> >     per generated interpreter and use non-static-methods instead, which
> >     should be better.
> >
> >     Anyway, I just want to be sure I am not stepping on anyone's toes if I
> >     check this in, since it makes small changes all over the place to
> >     ensure that the proper PyPy object is pushed onto the stack, etc.
> >
> >
> >     Niko
> >     _______________________________________________
> >     pypy-dev at codespeak.net <mailto:pypy-dev at codespeak.net>
> >     http://codespeak.net/mailman/listinfo/pypy-dev
> >     <http://codespeak.net/mailman/listinfo/pypy-dev>
> >
> >
> > ------------------------------------------------------------------------
> >
> > _______________________________________________
> > pypy-dev at codespeak.net
> > http://codespeak.net/mailman/listinfo/pypy-dev
>
> _______________________________________________
> pypy-dev at codespeak.net
> http://codespeak.net/mailman/listinfo/pypy-dev
>