My goal was mostly to hack around and try and get it working with the assumption that you guys would do it the right way sometime after Railsconf and I would throw my hack out.
I'll dig around in the Binder to see if I can uncover anything. Thanks, Steve On Thu, May 8, 2008 at 11:22 AM, John Lam (IRONRUBY) <[EMAIL PROTECTED]> wrote: > Steve Eichert: > > > This issue has been reported on Rubyforge (bug #20033). > > Thanks! > > > Can you point me in the general direction of where things would need > > to change in order to get this to work so I can hack around a bit? > > The high order bit here is that we're not delegating to the default DLR > binder in our implementation as much as we will in the future. A lot of > those features already exist in the DLR binder, so it's really a matter of > making that happen. > > That said, our binder is going to undergo some major work post RailsConf. > > FYI - although you're more than welcome to hack around and even create > patches that others can apply to their own private builds, we cannot accept > patches in the core IronRuby compiler today -- libraries are the only place > where we generally accept patches. Trivial patches for bug fixes are > excepted from the 'no patches to IronRuby core' policy. This is why we have > the distinction between IronRuby.dll vs. IronRuby.Libraries.dll > > Thanks, > -John > > _______________________________________________ > Ironruby-core mailing list > [email protected] > http://rubyforge.org/mailman/listinfo/ironruby-core >
_______________________________________________ Ironruby-core mailing list [email protected] http://rubyforge.org/mailman/listinfo/ironruby-core
