With the final release of the new Windows Ruby Installer almost out the
door, we need to start looking at compatibility, which Jari has done some
initial work on, but it does seem like there are other issues. The win32ole
mods are going to bite us. I like the idea of moving over some of our
windows calls to use FFI, I've been briefly checking that out, and it gives
us a lot of advantages (nice and clean, should work on JRuby as well as MRI
and Rubinius), but may have some more dependency issues that we need to
check out, definitely trading known issues for less known issues. FFI incurs
some penalty on perf, but that certainly might not matter given the current
state of our native library mish mosh.

-Charley





On Thu, Dec 3, 2009 at 6:27 PM, Jari Bakken <[email protected]> wrote:

> On Fri, Dec 4, 2009 at 2:03 AM, Alan Ark <[email protected]> wrote:
> > I’m guessing that a new version of win32ole.so might help the issue?
>
> That won't solve the problem, which is that the DL API (part of ruby's
> stdlib) is not compatible from 1.8 to 1.9. Recompilation might be
> needed for 1.9 as well. My quick fix was to just raise that error - I
> wasn't sure if it was being used since there are no unit tests for it.
> If you want to fix it, you'd need to:
>
> 1. Figure out how DL works in 1.9, or rewrite the Watir::Win32 module
> to use the FFI gem.
> 2. Possibly recompile the .so for 1.9.
>
> The FFI gem gives a much nicer API for interacting with C libraries,
> but it is of course yet another dependency..
> _______________________________________________
> Wtr-development mailing list
> [email protected]
> http://rubyforge.org/mailman/listinfo/wtr-development
>
_______________________________________________
Wtr-development mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/wtr-development

Reply via email to