Bill Dortch wrote:
What breaks is the ability to go to lower-level Java support, get a
JavaMethod object directly, and invoke it to get the original wrapped
JavaObject. Largely this capability was used in the old JI code to
implement the normal Java integration features; with most
>
> Looking at *all* objects implementing a java_class method. This would
> return an instance of java.lang.Class. No JavaXxx wrappers, possibly some
> helper methods added.
>
> Oops, explained this wrong. Would return the Rubified Java class (instance
of Ruby Class); get_class method on that woul
>
> What breaks is the ability to go to lower-level Java support, get a
> JavaMethod object directly, and invoke it to get the original wrapped
> JavaObject. Largely this capability was used in the old JI code to
> implement the normal Java integration features; with most of those
> "higher" Java s
Attached is a new patch for Java return-value coercion performance. It
solves the issues shown in the following benchmark:
BEFORE
Measure System.currentTimeMillis, int becoming Fixnum
6.254000 0.00 6.254000 ( 6.254000)
6.262000 0.00 6.262000 ( 6.262000)
6.177000 0.0
