Hi Shri,
I'm ready to start contributing (I signed the agreement and am now
able to run the specs on my machine).
I thought I'd focus on system/popen, but maybe there are simple things
that have a higher priority ?
cheers,
-- Thibaut
___
Ironruby-core
For mocking static CLR interfaces and abstract types, there is not much the DLR
can do. You need to create types on the fly which implement the CLR interface
you want to mock. I believe that is what most of the popular mocking frameworks
like NMock, Moq, RhinoMocks, etc do.
You could take a loo
Fixing the tags for IO.popen sounds fine.
Once you get a few changes in, it will be more useful to focus on bugs
affecting specific real-world apps since that enables real, useful scenarios.
However, starting off fixing RubySpec tags is good too as a ramp-up activity
since the problems are narr
Mark and I have spoke about this before, and really what we need is to pick a
.NET mocking framework and write a RSpec/Mocha-like wrapper around it, as the
APIs provided by Moq, NMock, etc need some rubification. As Shri said, the
DLR-itself won't help with this. Mark, does this make sense?
~js
