On 01/11/16 05:53, Yasuo Ohgaki wrote: > On Tue, Nov 1, 2016 at 11:53 AM, David Lundgren <dlundg...@syberisle.net> > wrote: >> > What if we made ArrayIterator transparently wrap all array's? > If you take a look at SPL array object code, you'll see why there are > so many missing functions. It's just pain for me to write new method > even with simple one.
So why don't people use SPL array objects where they want this repackaging of the procedural code? It has not gained traction as a full time replacement, but why not? > Can we get rid of some features from array objects? and make it > simpler? e.g. We don't need 2 ways to store array data, I suppose. > Why there are 2 ways? There are more ways to a lot of things than are actually needed, but stripping out 'duplicates' needs agreement on which are the better way. Personally I don't see the 'advantages' of completely remodelling the way the procedural functions work. If you want yet another user interface, build it as an object class. The bulk of the duplication is down to people adding their own view on how things should be done, and perhaps it is time to decide what is the core set of functions needed to handle simple structures and move everything else into optional extensions ... beginners don't need all the heavy stuff and I include Reflections in that ... A starter manual does not need the bulk of the code that is weighing down PHP today. -- Lester Caine - G8HFL ----------------------------- Contact - http://lsces.co.uk/wiki/?page=contact L.S.Caine Electronic Services - http://lsces.co.uk EnquirySolve - http://enquirysolve.com/ Model Engineers Digital Workshop - http://medw.co.uk Rainbow Digital Media - http://rainbowdigitalmedia.co.uk -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
