w.kelly at qut.edu.au
Sun May 18 08:23:02 EDT 2008
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?
More information about the Ironruby-core