There are two approaches: 1) wrap the unmanaged API in managed C++, or, 2) rewrite the library in managed code (IronPython?). Also, I think the Numeric library would be preferable to Numpy, although I'd bet Numpy has a larger user base. Option 1 could be done fairly quickly, but option 2 is the best long-term solution.
Several years ago I wrote a COM wrapper for many of the Numpy functions without too much pain. Wait, it was MFC. There must have been a lot of pain; I've just forgotten about it :-) Math: Do you (does anyone?) have an idea of what it would take to port Numpy, etc, to .NET? I'm not much of a C programmer (I can do it, but I can't really do big, UNIX-y projects), and have never studied the problems of porting it to MC++ or C++/CLI. _____ From: [EMAIL PROTECTED] on behalf of Martin Maly Sent: Fri 8/26/2005 11:11 AM The bug ... I assume it is in the "-X:TabCompletion" console, correct? I am going to look into it.
<<attachment: winmail.dat>>
_______________________________________________ users-ironpython.com mailing list users-ironpython.com@lists.ironpython.com http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
