> 3. A crazy idea is to arrange to port the modules to managed C++ > combined with a fake set of include files that makes the > modules really > link with IronPython rather than CPython. In theory, this > could let the > modules work well with IronPython with only a recompile required. This > could be really cool if it worked out, but I'm the least > confident that this option is truly possible.
I'll see your crazy idea, and raise you a ridiculously insane idea ;) Having done some of them, I now have a fair amount of respect for the crazy things that you _can_ do with the CLR ;) At a purely theoretical technical level, it _is_ possible to implement a 'python2X.dll' and provide unmanaged exports, where the implementation would work with the IP runtime. Of course, you would need to implement all of the CPython API on top of the IP runtime in a sane way for unmanaged consumers, but I think in the end the question is one of practicality, not technical possibility... not-volunteering-by-the-way 'ly, Brian Lloyd [EMAIL PROTECTED] V.P. Engineering 540.361.1716 Zope Corporation http://www.zope.com _______________________________________________ users-ironpython.com mailing list users-ironpython.com@lists.ironpython.com http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
