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
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
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.
--Chris
On 8/21/07, Martin
Martin Krauskopf wrote:
Chris Nelson wrote:
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.
The jruby-debug code I have is not checked in anywhere
Chris Nelson wrote:
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.
The jruby-debug code I have is not checked in anywhere yet. I'm not sure
where
Charles Oliver Nutter wrote:
Here's the proposed 1.1 roadmap Tom, Nick and I came up with this
afternoon. Add remove as you see fit, we'll try to iron it out.
- compiler complete
- AOT compilation working with jrubyc
- stdlib all precompiled
- gem install precompilation
- virtual file
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'
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 y
Chris Nelson wrote:
Hi Martin,
I recognize you from Netbeans Issuezilla :) It's great to hear someone
has already started on this. Sounds I'm starting at the same place you
did: looking at the ruby-debug-base c code and looking for the native
methods we would need to implement in JRuby. Ch
On 8/17/07, Chris Nelson <[EMAIL PROTECTED]> 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
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 tes
Chris Nelson wrote:
Hi Martin,
I recognize you from Netbeans Issuezilla :) It's great to hear someone
has already started on this. Sounds I'm starting at the same place you
did: looking at the ruby-debug-base c code and looking for the native
methods we would need to implement in JRuby. Ch
Hi Martin,
I recognize you from Netbeans Issuezilla :) It's great to hear someone has
already started on this. Sounds I'm starting at the same place you did:
looking at the ruby-debug-base c code and looking for the native methods we
would need to implement in JRuby. Charles, is this headius br
Martin Krauskopf wrote:
But it's one big mess, since I started in very similar position as
you. A lot of Java coding, some Ruby coding, 8+ year ago C coding. So
I'm still deleting and rewriting what I wrote as I'm getting into the
JRuby APIs (BTW purely documented guys! ;) )
Ups. Should be "p
Martin Krauskopf wrote:
Chris Nelson wrote:
Guys,
This sounds like an awesome list of stuff, but a feature that I think
would help a lot of with JRoR projects would be to improve the
debugging experience. Right now the only way to get JRuby on Rails
debugging to work in NetBeans is by setti
Chris Nelson wrote:
Guys,
This sounds like an awesome list of stuff, but a feature that I think
would help a lot of with JRoR projects would be to improve the debugging
experience. Right now the only way to get JRuby on Rails debugging to
work in NetBeans is by setting an undocumented proper
Kenneth McDonald wrote:
I think even half of that would more than justify a .1 release. Very
impressive!
Something I've been wondering about recently, that is definitely related
to a couple of the points below; any guesses as to what sorts of
speedups we can see in the future, and where these
Chris Nelson wrote:
Guys,
This sounds like an awesome list of stuff, but a feature that I think
would help a lot of with JRoR projects would be to improve the debugging
experience. Right now the only way to get JRuby on Rails debugging to
work in NetBeans is by setting an undocumented proper
Guys,
This sounds like an awesome list of stuff, but a feature that I think would
help a lot of with JRoR projects would be to improve the debugging
experience. Right now the only way to get JRuby on Rails debugging to work
in NetBeans is by setting an undocumented property in a config file. And
I think even half of that would more than justify a .1 release. Very
impressive!
Something I've been wondering about recently, that is definitely related
to a couple of the points below; any guesses as to what sorts of
speedups we can see in the future, and where these speedups will happen?
I
Here's the proposed 1.1 roadmap Tom, Nick and I came up with this
afternoon. Add remove as you see fit, we'll try to iron it out.
- compiler complete
- AOT compilation working with jrubyc
- stdlib all precompiled
- gem install precompilation
- virtual filesystem-inside-JVM (maybe) or h
21 matches
Mail list logo
