On Thu, Aug 5, 2010 at 8:26 PM, Robert Bradshaw <[email protected]> wrote: > On Thu, Aug 5, 2010 at 9:58 AM, Carl Witty <[email protected]> wrote: >> Once the C++/CLI backend works, a C# backend is a possible next step. >> All of the code generation for C# to interface with IronPython would >> be exactly the same as C++/CLI (modulo minor syntactic issues that can >> easily be localized). Even if the ultimate goal is a C# backend, I >> think that very little of the work on a C++/CLI backend would be >> wasted. > > The ultimate goal is really just Cython working (well) for IronPython, > right? How essential is C# generation (vs. C++/CLI) to that goal?
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. Carl _______________________________________________ Cython-dev mailing list [email protected] http://codespeak.net/mailman/listinfo/cython-dev
