[Ironruby-core] Signal.trap

Michael Letterle michael.letterle at gmail.com
Sun May 18 10:41:34 EDT 2008


PInvokes would, of course, make it non-portable to mono...or silverlight for
that matter.  So no, I don't think it's a good idea :)

On Sun, May 18, 2008 at 8:23 AM, Wayne Kelly <w.kelly at qut.edu.au> wrote:

> 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
> Ironruby-core at rubyforge.org
> http://rubyforge.org/mailman/listinfo/ironruby-core
>



-- 
Michael Letterle
[Polymath Prokrammer]
http://blog.prokrams.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/ironruby-core/attachments/20080518/48a8c295/attachment.html>


More information about the Ironruby-core mailing list