All the recent changes removed an attribute called cref (a singly linked list) with a direct RubyModule parent reference. I would expect this to screw up applying a patch (or svn update) but not to screw up your current work (other than if you marked cref transient, then you should mark parent transient).
-Tom On 7/11/07, Alan McKean <[EMAIL PROTECTED]> wrote:
I checked out the trunk again and everything seems to be okay. Except that there is a lot in RubyModule that wasn't there when I did the first version. I'm having trouble restoring the dispatcher when a persistent object faults back in. It seems to be an anonymous class. Is there a good way to restoring a dispatcher (I have marked the dispatcher transient)? On Jul 11, 2007, at 12:13 PM, Charles Oliver Nutter wrote: > Alan McKean wrote: >> It must be my environment. Now it even happens when I try to build >> the jar from the unmodified trunk code. >> This is the same stack trace that I get when I run any of the >> samples. > > Yeah, that's pretty core, and certainly doesn't appear to be broken > here. Update to current trunk (4006) and try again...I just built > and ran it and it's 100% passing tests. You might have caught us > between commits or something. > > - Charlie > > --------------------------------------------------------------------- > To unsubscribe from this list please visit: > > http://xircles.codehaus.org/manage_email --------------------------------------------------------------------- To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email
-- Blog: http://www.bloglines.com/blog/ThomasEEnebo Email: [EMAIL PROTECTED] , [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email
