Here's hoping they know what's wrong. I'm trying to put together a
test case, but it's almost a lost cause given the complexity of code
leading up to this point.
- Charlie
-- Forwarded message --
From: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
Date: Jan 14, 2006 10:02 AM
Subject: Your
This have certainly progressed since October!
We now have well over half the nodes in the AST being interpreted in a
purely iterative style. Where those nodes used to deepen the Java
stack by many frames (n multiples of 3 or 4 per node) they now are
processed and forgotten by JRuby, steadily incre
It's worse than I thought. I confirmed that the code runs correctly
under 1.5.0_05, and it does not run correctly under 1.4.2_06 or
1.4.2_10 unless run in interpreted mode. It appears there's a problem
with HotSpot under 1.4.2 that was never fixed and which is causing
this issue.
I'm a bit burned
Ugh. I've just spent the past two days hunting down impossible causes
for a null pointer, and it now appears likely that it's an Eclipse
compiler bug. When built using ant under Eclipse, which uses Eclipse's
Java compiler, I'm getting a null pointer exception on
state.getThreadContext().getRubyClas
