What Jimmy said. :D Ryan Riley
Email: ryan.ri...@panesofglass.org LinkedIn: http://www.linkedin.com/in/ryanriley Blog: http://wizardsofsmart.net/ Twitter: @panesofglass Website: http://panesofglass.org/ On Tue, Jan 26, 2010 at 3:17 AM, Jimmy Schementi < jimmy.scheme...@microsoft.com> wrote: > You’re correct Ivan. Today RCov isn’t even supported on IronRuby because it > uses a small c-extension. As Shri said previously, it’d be great if someone > could remove the dependency on the C-extension (easiest way is to write the > equivalent Ruby code … what Ryan is suggesting is a better way-long-term > goal for IronRuby to be compatible with FFI-based extensions), and then RCov > would work for code coverage of *only ruby code.* Now, imagine that was > done, and it was called ironruby-rcov … this wouldn’t work for code coverage > of your .NET code, so you’ll have to use the CLR code coverage tools. Only > at that point could you think about add CLR support to ironruby-rcov. > > > > Make sense now? > > > > ~Jimmy > > > > *From:* ironruby-core-boun...@rubyforge.org [mailto: > ironruby-core-boun...@rubyforge.org] *On Behalf Of *Ivan Porto Carrero > *Sent:* Tuesday, January 26, 2010 1:08 AM > *To:* ironruby-core@rubyforge.org > *Subject:* Re: [Ironruby-core] Did Something Changed Again in Spec... > > > > How does implementing FFI provide code coverage for the CLR, isn't that > mutually exclusive? Shouldn't FFI provide us with a way to use C-based > extensions? But C-based extensions won't know about the ironruby internals > etc. Just thinking out loud so feel free to correct me :) > > > > Also aren't the stacks produced by IronRuby a little different from the > stacks produced by MRI for example. > > > > To get code coverage for the CLR is that again the CLR profiling API you > would leverage? could somebody point me in the right direction? > --- > Met vriendelijke groeten - Best regards - Salutations > Ivan Porto Carrero > Blog: http://flanders.co.nz > Twitter: http://twitter.com/casualjim > Author of IronRuby in Action (http://manning.com/carrero) > > > On Tue, Jan 26, 2010 at 6:02 AM, Ryan Riley <ryan.ri...@panesofglass.org> > wrote: > > I asked about that earlier, as well, and got the response that it is not > covered. I believe one of the goals post-1.0 is to get Ruby FFI working. If > you'd like to see RCov working, you might write a patch to move RCov to Ruby > FFI so that it will work on IronRuby once FFI support is working. And if you > get that done, you might even be able to pitch in with the FFI > implementation. I, for one, would appreciate it. :) Of course, I could do > those, too, but I'm working on a few other things, atm. :) > > > > > Ryan Riley > > Email: ryan.ri...@panesofglass.org > LinkedIn: http://www.linkedin.com/in/ryanriley > Blog: http://wizardsofsmart.net/ > Twitter: @panesofglass > Website: http://panesofglass.org/ > > On Mon, Jan 25, 2010 at 2:15 PM, Mohammad Azam <li...@ruby-forum.com> > wrote: > > I was trying to make ironruby to perform code coverage for a .NET > assembly using rcov but it seems like it is not currently supported > yet.. > > -- > > Posted via http://www.ruby-forum.com/. > _______________________________________________ > Ironruby-core mailing list > Ironruby-core@rubyforge.org > http://rubyforge.org/mailman/listinfo/ironruby-core > > > > > _______________________________________________ > Ironruby-core mailing list > Ironruby-core@rubyforge.org > http://rubyforge.org/mailman/listinfo/ironruby-core > > > > _______________________________________________ > Ironruby-core mailing list > Ironruby-core@rubyforge.org > http://rubyforge.org/mailman/listinfo/ironruby-core > >
_______________________________________________ Ironruby-core mailing list Ironruby-core@rubyforge.org http://rubyforge.org/mailman/listinfo/ironruby-core
