<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div><blockquote type="cite"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin: 0px 0px 0px 0.8ex; border-left-width: 1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; padding-left: 1ex; position: static; z-index: auto;"><div dir="ltr">I would definitely be interested in helping, but don't exactly know where to start. We have a lot of users who would love to get access to numpy on our OSX and 64bit windows versions of our product. This is only going to become a bigger problem in the future since we will probably only have a 64bit version for Window in the next version of Rhino.</div>
</blockquote><div><br></div><div>I agree. Let's start a serious discussion about how to solve the lack of numpy in IronPython.</div><div><br></div><div>We could look into using ctypes (IronClad?) and wrap what already exists.</div>
<div><br></div><div>We could look into a cross-platform DLL drop-in replacement. </div><div><br></div><div>Between speed and compatibility, initially I'm most interested in compatibility. But speed should be a long term goal. <br></div></div></div></div></blockquote><div><br></div><div><br></div>I concur. Given the wide range of third party science and math libraries that uses numpy, completeness will bring us a good start even if it implies paying a high price on speed.</div><div><br></div><div><br></div></body></html>