[IronPython] IronPython + IronRuby + Known DLR Build
ben2004uk at googlemail.com
Sun May 25 16:26:11 PDT 2008
I think this would only work if you completely abstract away from the DLR.
My initial problem with that is this:
Main AppDomain references 126.96.36.1990 to use ScriptRuntime etc
IPAppDom refereences 188.8.131.520. Crossing AppDomain boundaries isn't
a problem because they are the same version.
RubyAppDoman references 184.108.40.206. When you have to pass your
ScriptRuntime (Engine, Scope whatever) back to the main appdomain I
think it will throw an exception.
Not having used AppDomains in a long time I might be wrong :)
On Sun, May 25, 2008 at 11:56 PM, Ivan Porto Carrero
<ivan at flanders.co.nz> wrote:
> You could treat it like plugins.
> that is have a rubybin folder and a pythonbin folder
> Load the correct assemblies in a different appdomain execute your code there
> and get the result back.
> For Michael this idea isn't new :) I'll that later this week in our dynamic
> script control to see how that works out.
> Any other more simple and elegant solutions are welcome of course
> On 26/05/2008, at 9:58 AM, Michael Foord wrote:
>> Hello Ben,
>> I don't have an answer, just to say that I have the same problem.
>> For our 'Dynamic Script Control' project we would like to develop (and
>> test with) for both IronPython and IronRuby.
>> This makes project structure "problematic".
>> I realise that at some point this will be a non-problem, but in the
>> meantime if anyone has any good ideas I'd like to hear them...
>> Michael Foord
>> Ben Hall wrote:
>>> Posted similar message onto IronRuby but I thought I would also ask
>>> you guys. My scenario is that I need to host IronRuby and IronPython
>>> within the same application. I thought this would be easy as they both
>>> are based on the DLR.
>>> However, you both appear to be at different stages of the DLR life and
>>> building against different sources. Is this the same internally? At
>>> the moment I can't see a way I can build both IronPython and IronRuby
>>> from the same DLR assemblies?
>>> At some point, I take it the DLR will merge into a single release and
>>> known assembly for other language providers and hosts to use instead
>>> of multiple different versions?
>>> In the mean time - what can I do? Is anyone doing this?
>>> Users mailing list
>>> Users at lists.ironpython.com
>> Users mailing list
>> Users at lists.ironpython.com
> Users mailing list
> Users at lists.ironpython.com
More information about the Users