|
From: Perry G. <pe...@st...> - 2006-01-19 01:21:44
|
On Jan 18, 2006, at 8:08 PM, Fernando Perez wrote: >>> Couldn't that last issue be well dealt with by the fact that today's >>> numpy is fairly subclassing-friendly? (which, if I remember >>> correctly, wasn't quite the case with at least old Numeric). >> Does that help? You aren't talking about the fast array subclassing >> numpy are you? I'm not sure what you mean here. > > What I meant was that by having good subclassing functionality, it's > easier to ward off requests for every feature under the sun. It's > much easier to say: > > 'this basic object provides a very small, core set of array features > where the focus is on raw speed rather than fancy features; if you > need extra features, subclass it and add them yourself' > > when the subclassing is actually reasonably easy. Note that I haven't > actually used array subclassing myself (haven't needed it), so I may > be mistaken in my comments here, it's just an intuition. > Yeah, that makes sense. I was confused by the reference to numpy. Perry |