Curt Hagenlocher wrote: > My two cents would be this: using Managed C++, try for source compatibility first.
Binary compatibility would be a great thing in the long term - after all, we don't want to run the risk of branching the target library's codebase! - but my gut feeling is that you're right, Curt: it would be much easier, at least as an exploratory first stage, to target source compatibility only. So perhaps we should start off in that direction. Does anyone know how this would impact the potential for Mono compatibility? Keith J. Farmer wrote: > NumPy would be cool :) That looks like a pretty popular choice generally - quite a few people have posted off-list saying the same. I'll get in touch with the NumPy developers. One further question for this list, before I create a repository and mailing list elsewhere for the project - what should the project be called? The best one we've come up with in-house is "RustPython" (IronPython, *C* extensions, you get the picture) and I'd be really grateful if someone could come up with a less appalling pun... Cheers, Giles -- 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
