From: Todd M. <jm...@st...> - 2004-02-10 13:40:56
|
On Mon, 2004-02-09 at 13:55, Tim Hochberg wrote: > I just noticed that the name asarray is considered obsolete and is to be > replaced with inputarray. Why is that? I'm not sure what gave you that impression; asarray() isn't obsolete. inputarray() was implemented "independently" and then I discovered afterward that it should have been called asarray(). At the time, I was hesitant to rename public functions so I just added the asarray() alias rather than renaming inputarray(). > The name asarray has a pretty > clear connection with it's behaviour (return it's argument as an array), > while I can come up with no such connection for inputarray. The best I > can come up with is that it's often used on the inputs of functions to > coerce them to arrays, but that seems a pretty tenuous connection. Is > there a better reason? Nope. > Am I just being obtuse? > > -tim > > > > ------------------------------------------------------- > The SF.Net email is sponsored by EclipseCon 2004 > Premiere Conference on Open Tools Development and Integration > See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. > http://www.eclipsecon.org/osdn > _______________________________________________ > Numpy-discussion mailing list > Num...@li... > https://lists.sourceforge.net/lists/listinfo/numpy-discussion -- Todd Miller <jm...@st...> |