Re: Pseudo-objects (methods on arrays, strings, etc.)
| From: | Lester Caine | Date: | Thu, 19 Jul 2012 16:36:18 +0000 |
| Subject: | Re: Pseudo-objects (methods on arrays, strings, etc.) | ||
| References: | 1 2 3 4 5 6 7 8 9 10 11 12 13 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-61499@lists.php.net to get a copy of this message | ||
Pierre Joye wrote:
So a few people want this therefore we all have to have it? We need to sort out a list of priorities and then perhaps see if there is a majority demand for each? Since somebody will obviously rewrite key libraries using this 'sexy' stuff, we are all then forced to have to work with it even if we can ignore it in our own code. ONE of these days I'd like to get back to putting some new functions in my own code base. I'm still working on a long list of 'strict' warnings across several projects and libraries :( Work that I don't make any money from but am having to do simply to keep things simple when the NEXT changes happen! -- 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.ukshould still work. All the string API methods need to be available onevery pseudo-object regardless of the type. So I don't see any "cleanup" here either. I do, and again this is purely a theoretical discussion right now. However I find disturbing the resistance to such a proposal given that what I hear from our users is a total support to introduce this concept to PHP, even step by step. So we should better begin to see where are the technical bottlenecks and figure out a way to solve them instead of arguing about whether we should do it or not. Because we will have to do it, whether we like it or not.