Re: [RFC] Deprecate PEAR/PECL & Replace with composer/pickle

On 03/09/16 17:11, Rowan Collins wrote: >> A starting point for a replacement for PEAR might well be a style guide >> that lays out just how one should build a modern suite of code. My >> stumbling block deciphering owncloud is just how one does work out >> exactly what code has been loaded and from what files. Irrelevant if >> things just work, but when debugging an installation, the code flow >> should be easy to establish! > > As mentioned, that's exactly what PHP-FIG is doing; what you're talking > about is exactly what PSR-1, PSR-2, and PSR-4 describe. > > You may not agree with the choices they made, like the people that made > them, or approve of the processes they used, but all that would be just > as likely if they happened to be hosted on a sub-domain of php.net. So this RFC is simply proposing that PHP-FIG becomes the standard for writing PHP code? -- 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