I'm sort of working thru problems one at a time and fixing them as we can. We don't even really have a solid yardstick of how far there is to go yet, I don't think. The c version of ruby-debug didn't really have a solid set of test cases to start with (tho I'm trying to add some as I go) so we don't really know where we stand. So I'm not sure we're in a position to commit to anything. Also, I'm just doing this in my random bits of free time and that can evaporate on a dime, sadly. I can give my standard open source volunteer answer: it will be ready when it's ready ;)
That said, I did make some progress with var global yesterday and uncovered an issue (should be easy to fix) in JRuby with global variables. Some of them ($? for example) return java null instead of RubyNil when accessed. This causes NPEs in JRuby. Running 'var global' from rdebug tries to list and print all of them and blows with NPE. Either RubyGlobal needs to check for null and return RubyNil or else ThreadContext needs to initialize its lastExitStatus property to RubyNil. Not sure which way is preferred, but either should be easy to fix. I should be able to do it today if you want to let me know which way to go, and where the right place to add a test case for it is. Otherwise, if you can do it more quickly I can work on other stuff. As far as my patch, I agree with Martin we're still in early stages but it does seem rather an innocuous patch and would alleviate us manually keeping it around when we update from trunk. We also need to talk about how best to package this up as a gem, but that's another conversation. --Chris On 9/29/07, Charles Oliver Nutter <[EMAIL PROTECTED]> wrote: > > Martin Krauskopf wrote: > > Yes this one is needed for us. But I would wait with sending patches to > > JRuby. Currently jruby-debug is very raw rewrite from native ruby-debug. > > Is very likely that I missed something somewhere. So I would wait until > > we get a little bit further with jruby-debug. For now we two can live > > with patching the JRuby on our machines. Note that I've added the note > > about this patch to the jruby-debug's README few days ago: > > > > http://debug-commons.rubyforge.org/svn/jruby-debug/trunk/README > > > http://debug-commons.rubyforge.org/svn/jruby-debug/trunk/jruby-patch.diff > > We'll be happy to apply whatever patches you need at such time as you > think you're really ready to go or there's a big show-stopper you need > fixed on trunk. > > And btw...it would be great if this could be done and working for the > 1.1 release, and any changes backported to the 1.0 branch. So is a month > enough time to get it solid? > > - Charlie > > > --------------------------------------------------------------------- > To unsubscribe from this list please visit: > > http://xircles.codehaus.org/manage_email > >
