On 04/03/16 11:36, Rowan Collins wrote: > Lester Caine wrote on 04/03/2016 11:19: >> 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'm not sure I follow. What do you mean by "comment 'var' entries"? To > my knowledge, /** @var ... */ is the correct notation for PHPDoc for a > property, whatever its visibility, but maybe you're talking about some > other comments?
Where the variables are using in @var comments or in other comment documentation, adding private or making other changes related to the variable being changed ... cost of changing the 'var' may be low, but then tidying up the documentation may have a higher time cost? One really needs to address the whole picture for each change. >> 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? > > This much I agree with. I see no urgency to batch update, even if the > cost of doing so is low. Exactly :) -- 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
