On 03/03/16 13:24, Rowan Collins wrote: >> Actually my problem is even more simple than that - although it may be >> possible to further filter the lookup for 'var ' ( note the space ) many >> of the results are simply not text that needs changing. > > The script that Colin linked > (https://gist.github.com/colinodell/5fb5e5d474674f294a38) uses an > in-language tokenizer, not just text find-and-replace, so this is a > solved problem. If this turns out to not be smart enough, one built on > top of Nikita's PHP-Parser project would be pretty easy as well: > https://github.com/nikic/PHP-Parser/
My main reason for not taking that brute force approach is actually the same. Many of the comment 'var' entries relate to the use of the identified var. So changing one without the other just creates more problems? It's the documentation style from 15 years ago that is just as important to maintain and something that is not on the current roadmap? The whole process needs addressing not just one element. I've no problem that as code is tidied these elements get replaced and that is already part of my own process. It's simply a matter of just how 'essential' it is that this is done, and I don't see any pressing need as yet to remove var? -- 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
