On Tue, Aug 10, 2010 at 9:56 PM, David Cournapeau <[email protected]> wrote: > On Fri, Aug 6, 2010 at 1:55 PM, Carl Witty <[email protected]> wrote: > >> For IronPython running under Microsoft's .NET implementation for >> Windows, as far as I know there are no problems with C++/CLI. For >> IronPython running under Mono on non-Windows platforms, C++/CLI >> doesn't help at all; there are no implementations of C++/CLI on >> non-Windows platforms and no effort toward making an implementation. >> So the purpose of a C# backend would be to support Mono. > > I would think that it would also help for a jython backend, as there > is no equivalent to C++/CLI in the java land AFAIK, and changing from > C# to java back in cython should be much easier. > > For people who are not so familiar with C++/Cli, could you expand a > bit more on the choice of C++/CLI vs C# as a first step ? The "extern" > part sounds logical (a VM like the CLR or the JVM has strong strong > ABI constraints), but the exception part not so much. Also, what does > C++/Cli buys you instead of pure C or C++ (through p/invoke) ? CLI is > gc aware, right ? I am also curious about the differences between > C++/CLI vs p/invoke (the latter having an equivalent in the java),
I'd imagine that the primary goal of using CLI is that IronPython objects live in the CLI environment, and the goal is to play nice with that. I'm not very familiar with all of this though, so would be curious to hear more details myself. - Robert _______________________________________________ Cython-dev mailing list [email protected] http://codespeak.net/mailman/listinfo/cython-dev
