Could you please file bugs for all the workarounds you've needed (if they are not filed yet)? I'll take a look at Signal#trap tomorrow.
Thanks, Tomas -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Wayne Kelly Sent: Sunday, May 18, 2008 5:23 AM To: [email protected] Subject: [Ironruby-core] Signal.trap After various workarounds, I can now run the rails app to the point that it gets through all of the gems infrastructure and starts running actual rails specific code. Unfortunately the first thing that it calls is Signal.trap which is currently unimplemented. I have an implementation of Signal.trap from Ruby.NET but it relies on Pinvoke to call functions in msvcrt How do you feel about this kind of code in IronRuby? Cheers, Wayne. _______________________________________________ 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
