Tomas.Matousek at microsoft.com
Mon May 19 03:39:31 EDT 2008
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.
From: ironruby-core-bounces at rubyforge.org [mailto:ironruby-core-bounces at rubyforge.org] On Behalf Of Wayne Kelly
Sent: Sunday, May 18, 2008 5:23 AM
To: ironruby-core at rubyforge.org
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?
Ironruby-core mailing list
Ironruby-core at rubyforge.org
More information about the Ironruby-core