On 26/08/15 20:02, Stanislav Malyshev wrote: >> Just because there is a function, which does not exactly roll off the >> > tongue (plus the fun of the needle/haystack ordering issue), does not >> > mean it gets used (even if it is the correct thing to use).
> As it looks to me, in order to fix the fact that people are > not using existing function (which completely satisfies the > requirements), because people do not read the docs, the proposal is to > create another function (which nobody knows about without reading the > docs) that does the same? If so, I'm not sure how that is supposed to > help anything. We have had discussions before over the various 'complaint' sites and how in many cases the 'complaints' get more prominence than the actual current 'solution'. Yet again, what is needed rather than a manual describing each function individually since for example one would not look under 'array_' for a solution to this problem, is a 'best practice' example which can help even those of us who are stuck with legacy practices which COULD be improved with better modern samples. -- 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
