On 6/23/06, Keith Goodman <[EMAIL PROTECTED]> wrote:
On 6/22/06, Bill Baxter <[EMAIL PROTECTED]> wrote:
> On 6/22/06, Ed Schofield <[EMAIL PROTECTED]> wrote:
>
> >
> > On 22/06/2006, at 12:40 AM, Bill Baxter wrote:
> >
> > > Actually I think using mat() (just an alias for the matrix
> > > constructor) is a bad way to do it.  That mat() (and most others on
> > > that page) should probably be replaced with asmatrix() to avoid the
> > > copy.
> >
> > Perhaps the 'mat' function should become an alias for 'asmatrix'.
> > I've thought this for a while.
>
>
> That makes sense to me.  As far as I know, asmatrix() defaults to calling
> the constructor if it can't snarf the memory of the object being passed in.
>
> So, go on, shoot Ed and me down! :-)

I can anticipate one problem: the Pirates will want their three-letter
abbreviation for asarray.

arr() me maties!

Will functions like rand and eye always return arrays? Or will there
be a day when you can tell numpy that you are working with matrices
and then it will return matrices when you call rand, eye, etc?

I don't disagree there's a need, but you can always make your own:

def mrand(*vargs):
    return asmatrix(rand(*vargs))

def meye(N, **kwargs):
    return asmatrix(eye(N,**kwargs))

--bb
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Numpy-discussion mailing list
Numpy-discussion@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/numpy-discussion

Reply via email to