From: Wayne Vucenic <nightphotos@...>
Date: 2005-09-27T05:54:50+09:00
Subject: Re: Ruby and CLR interactions

------=_Part_19589_29887600.1127768088626
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Hi John,
 I'm really glad to see that someone is working on a shim for CLR 2.0!

>> But if I don't initialize
>> the CLR until after my Ruby program has already started running, I'm
going
>> to run into some nasty corner cases. For example, what if someone called
a
>> COM object via win32ole? By the time we get to my shim, COM will have
been
>> initialized already and there's not a lot I can do other than fail when =
I
>> attempt to initialize COM again.

>> I was wondering if folks would have some ideas about *how* I can declare
my
>> threading requirements at startup time?
 I'm not sure I'm clear on when you need to declare the threading
requirements.
Would doing something like this as the first 2 lines in the .rb file work?
 require 'clrshim'
setSTA
 where 'setSTA' (or 'setMTA') is a method your shim defines.
 as long as any win32ole stuff came after this, we should be OK.
 Or am I overlooking something?
 Wayne Vucenic
No Bugs Software
"Ruby and C++ Agile Contract Programming in Silicon Valley"

------=_Part_19589_29887600.1127768088626--