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! :-)
--Bill
All the advantages of Linux Managed Hosting--Without the Cost and Risk! Fully trained technicians. The highest number of Red Hat certifications in the hosting industry. Fanatical Support. Click to learn more http://sel.as-us.falkag.net/sel?cmd=lnk&kid=107521&bid=248729&dat=121642
_______________________________________________ Numpy-discussion mailing list Numpy-discussion@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/numpy-discussion
