David Huard (el 2008-07-29 a les 12:31:54 -0400) va dir:: > Silent casting is often a source of bugs and I appreciate the strict > rules you want to enforce. However, I think there should be a simpler > mechanism for operations between different types than creating a copy > of a variable with the correct type. > > My suggestion is to have a dtype argument for methods such as add and subs: > > >>> numpy.ones(3, dtype="t8[Y]").add(numpy.zeros(3, dtype="t8[fs]"), > dtype="t8[fs]") > > This way, `implicit` operations (+,-) enforce strict rules, and > `explicit` operations (add, subs) let's you do want you want at your > own risk.
Umm, that looks like a big change (or addition) to the NumPy interface. I think similar "include a dtype argument for method X" issues hava been discussed before in the list. However, given the big change of adding the new explicit operation methods I think your proposal falls beyond the scope of the project being discussed. However, since yours isn't necessarily a time-related proposal, you may ask what people think of it in a separate thread. :: Ivan Vilata i Balaguer @ Intellectual Monopoly hinders Innovation! @ http://www.selidor.net/ @ http://www.nosoftwarepatents.com/ @
signature.asc
Description: Digital signature
_______________________________________________ Numpy-discussion mailing list Numpy-discussion@scipy.org http://projects.scipy.org/mailman/listinfo/numpy-discussion
