I'll look at the ruby-debug trunk code and see what I can figure out. I wasn't clear from your post, are you saying your code is checked into JRuby trunk now? If so, where? I'm not seeing it.
--Chris On 8/18/07, Martin Krauskopf <[EMAIL PROTECTED]> wrote: > > Chris Nelson wrote: > > Cool. It's a plan! > > > > Martin, here's one idea for how we can collaborate. Since test cases > > are my favorite kind of documentation, maybe we can us them to help us > > get started. Here are some different approaches we could use depending > > on where things are at now: > > > > Good: If your code does not have test cases perhaps I can help write > > them and thereby come to an understanding of it. > > Better: If there are test cases already, I'll start by reading and > > running them and come up to speed that much more quickly. > > Best: If you have some failing test cases for code not yet implemented, > > I'll start in on trying to make them pass. > > This would be the best, I think. Since what I'm starting with is test > cases in ruby-debug itself. But unfortunately there are not too much of > them ($ruby-debug-trunk/test/test-ruby-debug.rb only). > So if you would checkout ruby-debug's trunk and start to write tests > there they would help not only to jruby-debug but also to ruby-debug > itself and to (s|r)ruby-debug implementation in the future > (smalltalk|rubinius) :) > Your testcases would help me also understand all corners of non-C > (ruby-debug-cli) part. > > Note that I spent only approximately one week with brute-force rewriting > so I'm happy that I can run the code without zillion of Java/Ruby > exceptions. > I believe that I'll have time next week to take a look at it again. > > Also feel free to join whatever subproject in debug-commons. We really > need contributors there ;) > > Regards, > m. > > --------------------------------------------------------------------- > To unsubscribe from this list please visit: > > http://xircles.codehaus.org/manage_email > >
