NumPy is largely about speed, and going through extra interop layers can really bite into that (my $0.02).
I think the suggestion for a smaller module to start with was about learning about compatibility with a more manageable chunk of code than the many, many lines of deep number-crunching that NumPy has accumulated, but maybe a few sections of compatibility there (i.e. limited part of the API) would be a similarly tractable goal? Wrapping the plain-C in COM would be a good way to test implementation compatibility, if your plan is to ported raw C to C++, so that the DLR/CLR can get some hooks in and go-quicka: the COM-wrapped CPy extensions may be faster to develop, if not performing as quickly, and if your C++ ports behave the same, you have pretty good confidence. Along the way, they'll help point out what's the framework and what's your code, especially if you can run the same test-cases through straight CPy. Wrapping all the way back through Mono seems an odd goal - isn't IPy compatible enough with CPy in source that your business apps would be light to port back to Cpy-land, if you're on Posix already anyway? For some purposes, it really makes sense, but a NumPy implementation for IPy for Mono? Seem to me that going that deep this soon will make you a valuable contributor to low-level compatibility testing... but I don't have the whole picture of where you're going. If you're going to alloy FePy, would that make a type of SteelPython? - a happier compound than Rust! Cheers, -- Matt ________________________________ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Giles Thomas Sent: Monday, October 15, 2007 9:17 AM To: Discussion of IronPython Subject: Re: [IronPython] Announcement: Project to get some CPython C extensions running under IronPython Davy, What would the issues be with NumPy - just the size of the API that would have to be wrapped? I must admin that my biggest concern with this would be getting everything running under Mono... Cheers, Giles Davy Mitchell wrote: On 10/12/07, Giles Thomas <[EMAIL PROTECTED]> <mailto:[EMAIL PROTECTED]> wrote: Python and .NET, but also the existing CPython C extensions. Hi Giles, Sounds like a good idea and the approaches mentioned seemed solid. One strategy I was considering for a port of my Mood News site to Ironpython (but not tried yet!) is wrapping a CPython Lib into a COM object using the win32 stuff and getting it into .Net via the COM interop support. Maybe not practical for Numpy :-) Does have the advantage of not having to modify the original lib... Cheers, Davy -- Giles Thomas MD & CTO, Resolver Systems Ltd. [EMAIL PROTECTED] +44 (0) 20 7253 6372 We're hiring! http://www.resolversystems.com/jobs/ 17a Clerkenwell Road, London EC1M 5RD, UK VAT No.: GB 893 5643 79 Registered in England and Wales as company number 5467329. Registered address: 843 Finchley Road, London NW11 8NA, UK
_______________________________________________ Users mailing list Users@lists.ironpython.com http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
