On 02/09/16 20:32, Davey Shafik wrote: > I'm also proposing voting choices around the optional/default introduction > of composer/pickle.
I've just been through an exercise to give PHP_CodeSniffer a go on my code base. I've not worried too much about that in the past since Eclipse in general flags style problems as well as simple errors. This is a package that SUSE does not support, so the current install path is just PEAR. I don't see packages like this as a library that my sites use. It is a stand alone tool ( and a command line one at that :) ) so how would loading that be managed if PEAR is not available? I had the problem having loaded the tool in finding the rule sets so that I could create one suitable for my own application. That is dictated by SUSE was was not quite where I expected it, so this may also be something that an alternative tool loader might be able to help with? Main reason for loading was to give some of the PSR rule checks a try to see just what affect they would have on the code, but I don't think this approach will help with the structural changes needed? -- 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
