Karl Nelson

Proxing has some big speed implications over a morph. There are a lot of implications with referencing as the typing model for isinstance would have major implications. This is hit...

Also my resistence to the name jpype.jvm is I consider that to be where the jvm controls belong. I couldn't move them due to compatiblity. But I consider anything that...

I should point out the lookups for method resolution are in C++ currently and use much faster methods than you can do when testing from within Python. It really isn't...

It isn't before the JVM is running that I am worried about. Most of the behaviors that happen when you mix objects before or after the JVM is created. For...

I worked a bit on the prototype last night to see if it is workable. I am going with JForward as proxy is a very different thing with a specific...

Example code: ``` import jpype # This will be used for morphed types, everything must have a base tree # We need to make sure these are fast lookup so...

Seems like a total of 8 pointers should cover the needs for most morphs. 2 for base object, 2 for weak and dict, 2 for payload, and 2 hidden for...

See https://github.com/Thrameos/jpype/blob/forward/forward.py for the current state.

It may be possible to just have the JImplements check it it is currently a forward and set the deferred flag accordingly.

If it appears reasonable that I can start cutting code on the morphing which will change it from pure Python to actually mucking with the CPython internals. That will cut...