Martin Krauskopf wrote:
So it says all ;) What would tremendously help me in this stage are unit test for ruby-debug-base (as I wrote already) which is one layer above the code I'm working on (i.e. unit test written in Ruby). It would also helped a lot to C ruby-debug team (Kent Sibilev and for some time already, Rocky Bernstein as I understand it). Since I'm already passing their test suite, but really simple now. Currently somehow and sometime is working 'next', 'step' and 'break' commands for super-simple programs. But that was the worse to reach, I think. Now I should be able to proceed more quickly, since I learned basic of JRuby APIs and I'm able to map to it from C Ruby API. Also I would like to start to understand what the code I'm rewriting actually does :) But I do not have too much time these days, since we are approaching NetBeans 6 Beta 1, which is top priority now. But from time to time I will work on it (I hope).
I would officially call on the JRuby community to help out Martin here. He's got an excellent start, but he's splitting time between getting jruby-debug and NetBeans out the door...you can guess which takes priority, and we certainly don't want to impact the excellent work he's doing on NetBeans.
Martin and others: please keep us posted on any changes necessary in core. I don't know what else of internal Ruby APIs ruby-debug uses, so I only ever wired up the event hook logic. If there's something additional we need to add, let us know.
- Charlie --------------------------------------------------------------------- To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email
