From: Bret Pettichord <bret@...>
Date: 2004-02-21T02:00:49+09:00
Subject: Re: Blocking Calls on Win32 Ruby

At 07:34 PM 2/17/2004, Shashank Date wrote:
>Not really ... if you could show the code we can talk about the specifics.
>HTH,

Well, i am porting 18,000 lines of ruby originally written on the Mac so 
that they will run on Windows. Do you want me to send all of it to you?

OK. Here's an update. I've got all that code working (except for a few 
minor problems) using the cygwin ruby. That's cool.

The problem is that i need to hook up that code, which is a web 
application, to some ruby scripts that drive Internet Explorer's COM 
interface. Guess what? That code will only work on mswin32 ruby because 
cygwin doesn't support OLE/COM.

This was what i want to do:
- start the web application in a separate thread/process
- run the tests using IEC
- stop the web application.

My head has been hurting all day as i try to go back and forth from 
thinking in cygwin ruby vs mswin32 ruby. I think i can do this if i put the 
main thread in cygwin ruby and then have it spawn one thread/process to run 
the server in cygwin ruby and other thread/process to run the iec tests in 
mswin32 ruby.

Honestly, it is making me think that Python looks pretty good in comparison.

Bret


_____________________________________
  Bret Pettichord, Software Tester
    Book - www.testinglessons.com
    Consulting - www.pettichord.com
    Blog - www.io.com/~wazmo/blog

    Homebrew Automation Seminar
    March 19, Redmond, Washington
    www.sasqag.org/99days/#automation