Chris Nelson wrote:
Hi Martin,

I might have some time to actually work on this stuff tomorrow, any chance you could share you code in whatever state it's in so I have something to look at? I'll also play around and see if I can write any useful testcases for ruby-debug, time permitting.

Hi Chris,

it's a little bit later than 'tomorrow' ;), but I've committed the code into debug-commons[1] project. Quoting README there:

====
This is really far from complete. Rather backup and sharing for the
case, someone would like to jump-in in this *very* early stage. A lot of
code is/might_be just wrong. Better to go away and return in few
days/weeks :)

Please contact me at [EMAIL PROTECTED] if you would like to
contribute, retake, send patches ... cooperate in whatever manner. See
the 'initiating' thread on the [EMAIL PROTECTED] mailing list.

http://archive.jruby.codehaus.org/dev/ef98118a0708171132u2bb08358q179a6d29235faadd%40mail.gmail.com
====

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).

Regards,
        m.

[1] http://rubyforge.org/projects/debug-commons


---------------------------------------------------------------------
To unsubscribe from this list please visit:

   http://xircles.codehaus.org/manage_email

Reply via email to