On 27/04/15 09:15, Benjamin Eberlei wrote: >> There was a lot of discussion about this topic. Right now, unless >> > there's a proposal to fix it that works, I don't see what can be done >> > about it. >> > > It should be possible to write something with PHP Parser detecting all the > occurances of "String/string" class usage to at least give a worklog of > entries that need to be changed, or maybe generate a patch file that can be > applied to the code base after review.
We have already had a similar incidence of this problem with the date/time stuff. The main problem then was it being introduced at the wrong time. PHP7 is the right time but switching the names being use is not an option. string IS probably the most difficult one, but any good IDE will allow all of the existing names to be changed. What is possibly an annoyance here is that this IS simply blocking the usage, rather than providing a functional replacement? Other 'priorities' seem to have pushed a single string handling solution back down the pile :( The question should perhaps be does any of the third part string classes provide a 'pear' style alternative which can be later be converted to an internal function set? -- 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
