RE: [IronPython] RE: Numpy port

2005-09-01 Thread msurel
7;y' .. so you can go through each > >combination > of i/y that occurs in each part. > >___ > > > >From: [EMAIL PROTECTED] on behalf of Thane > >Sent: Wed 8/31/2005 2:00 PM > >To: 'Discussion of IronPython' > >

RE: [IronPython] RE: Numpy port

2005-08-31 Thread J. Merrill
MAIL PROTECTED] on behalf of Thane >Sent: Wed 8/31/2005 2:00 PM >To: 'Discussion of IronPython' >Subject: RE: [IronPython] RE: Numpy port > >essential_parts = "py,pyth,python".split(',') >other_parts = "net,i,ir,iron,fe,ferrous,-anything-but-shar

RE: [IronPython] RE: Numpy port

2005-08-31 Thread Keith J. Farmer
It's okay to interchange 'i' and 'y' .. so you can go through each combination of i/y that occurs in each part. From: [EMAIL PROTECTED] on behalf of Thane Sent: Wed 8/31/2005 2:00 PM To: 'Discussion of IronPython' Subje

RE: [IronPython] RE: Numpy port

2005-08-31 Thread Thane
(Doesn't include "Pyronic" which I kinda like.) _ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Keith J. Farmer Sent: Wednesday, August 31, 2005 3:46 PM To: Discussion of IronPython Subject: RE: [IronPython] RE: Numpy port "Pynet".

RE: [IronPython] RE: Numpy port

2005-08-31 Thread Keith J. Farmer
"Pynet".. then instead of "Pythonistas", we could call ourselves "goobers". (that's okay..) From: [EMAIL PROTECTED] on behalf of Anthony Tarlano Sent: Wed 8/31/2005 11:02 AM To: Discussion of IronPython Subject: Re: [IronPyth

Re: [IronPython] RE: Numpy port

2005-08-31 Thread Anthony Tarlano
I was thinking about the name thing again and I really like: pythonet   ;-) (sorry if this brings an onslaught of new naming messages)On 8/31/05, Ken Manheimer <[EMAIL PROTECTED] > wrote:just incidentally:On 8/27/05, Thane < [EMAIL PROTECTED]> wrote:> [...]> I think that "numpy" is the import na

Re: [IronPython] RE: Numpy port

2005-08-31 Thread Ken Manheimer
just incidentally: On 8/27/05, Thane <[EMAIL PROTECTED]> wrote: > [...] > I think that "numpy" is the import name for the "Numerical" library > originally created by Paul Dubois. it's worth noting that it was our jim hugunin who originated numerical python. from http://www.pfdubois.com/numpy/ht

RE: [IronPython] RE: Numpy port

2005-08-31 Thread Morgan Martinet
> I wouldn't call the FORTRAN "legacy code". People are still using BLAS > and such because the FORTRAN code performs better. These routines have > been rewritten many times in C, C++, and Java and people still use the > FORTRAN simply because it does a better job. Numerical solutions are > wha

RE: [IronPython] RE: Numpy port

2005-08-31 Thread Michael Gogins
To: [EMAIL PROTECTED], 'Discussion of IronPython' Subject: RE: [IronPython] RE: Numpy port I had a look at this a few months ago. Both numarray and Numeric use an amorphous char array for storage. A simple wrapper would mean a lot of unmanaged memory moving around... not a desirable sit

Re: [IronPython] RE: Numpy port

2005-08-31 Thread Paul Barrett
On 8/31/05, Jeffrey Sax <[EMAIL PROTECTED]> wrote: I had a look at this a few months ago. Both numarray and Numeric use anamorphous char array for storage. A simple wrapper would mean a lot ofunmanaged memory moving around... not a desirable situation. True. It seems to me that a rewrite using gen

RE: [IronPython] RE: Numpy port

2005-08-31 Thread Jeffrey Sax
__ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Thane Sent: August 27, 2005 6:24 PM To: 'Discussion of IronPython' Subject: [IronPython] RE: Numpy port There are two approaches: 1) wrap the unmanaged API in managed C++, or, 2) rewrite the library in managed code (Ir

Re: [IronPython] RE: Numpy port

2005-08-28 Thread Drew Moore
Paul Barrett wrote: IronPython provides an excellent opportunity to design and implement a multidimensional array module that uses OO language features for fast and efficient code. Let me know if you would like me to elaborate on this some more. I know I'd be interested. I love numarray. Pa

RE: [IronPython] RE: Numpy port

2005-08-27 Thread Keith J. Farmer
I think it'd be a good project. Used properly, the CLR's already been shown to have decent speed for numeric calculations (and C# has access to pointers). I was considering getting the OO Numerical Methods in Java & Smalltalk book at some point, and porting the Java source to J#. Python's got a f

Re: [IronPython] RE: Numpy port

2005-08-27 Thread Paul Barrett
Option 1 is the way to go if you want a quick and dirty multidimensional array module that currently has a lot of community support. Numarray/Numeric 3 was designed with the C programming language in mind and is therefore constrained by C's lack of object-oriented features. The Numarray code can

RE: [IronPython] RE: Numpy port

2005-08-27 Thread Thane
Correction: the library I was thinking of is called "Numarray". See http://www.stsci.edu/resources/software_hardware/numarray I think that "numpy" is the import name for the "Numerical" library originally created by Paul Dubois. _ Also, I think the Numeric library would be prefer

RE: [IronPython] RE: Numpy port

2005-08-27 Thread Keith J. Farmer
Title: RE: [IronPython] Environment.Platform? and a bug It’s been ages; all I remember is Numpy.   - Keith J. Farmer [EMAIL PROTECTED] From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Thane Sent: Saturday, 27 August 2005 15:24 There are two approaches

[IronPython] RE: Numpy port

2005-08-27 Thread Thane
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 b