[Ironruby-core] Signal.trap

Wayne Kelly w.kelly at qut.edu.au
Mon May 19 05:04:57 EDT 2008

> From: Tomas Matousek [Tomas.Matousek at microsoft.com]
> Sent: Monday, 19 May 2008 5:39 PM
> To: ironruby-core at rubyforge.org
> Subject: Re: [Ironruby-core] Signal.trap

> Could you please file bugs for all the workarounds you've needed (if they are not filed yet)?

I've submitted all that make sense to submit at this stage.
Others that result from patches on top of uncomfirmed patches are best not to submit yet as it's not always clear where the bug actually lies.

The most pressing issue for me at this stage is that of internal file path representation '/' vs '\' (from my previous email).

Any initial thoughts?

I suspect we will find less resistence if we go with '/' as there's a lot of gems code that explicitly uses '/'

Cheers, Wayne.

More information about the Ironruby-core mailing list