Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:95604 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 88868 invoked from network); 3 Sep 2016 18:44:45 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 3 Sep 2016 18:44:45 -0000 Authentication-Results: pb1.pair.com smtp.mail=lester@lsces.co.uk; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=lester@lsces.co.uk; sender-id=unknown Received-SPF: error (pb1.pair.com: domain lsces.co.uk from 217.147.176.214 cause and error) X-PHP-List-Original-Sender: lester@lsces.co.uk X-Host-Fingerprint: 217.147.176.214 mail4-2.serversure.net Linux 2.6 Received: from [217.147.176.214] ([217.147.176.214:38763] helo=mail4.serversure.net) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 46/93-32927-A1A1BC75 for ; Sat, 03 Sep 2016 14:44:44 -0400 Received: (qmail 16182 invoked by uid 89); 3 Sep 2016 18:44:39 -0000 Received: by simscan 1.3.1 ppid: 16174, pid: 16178, t: 0.0729s scanners: attach: 1.3.1 clamav: 0.96/m:52/d:10677 Received: from unknown (HELO ?10.0.0.7?) (lester@rainbowdigitalmedia.org.uk@81.138.11.136) by mail4.serversure.net with ESMTPA; 3 Sep 2016 18:44:39 -0000 To: internals@lists.php.net References: <2e2e7a2d-4459-c59f-6552-b01314a06b2f@lsces.co.uk> <82d74255-4118-46f4-c073-35e3b224fef8@gmail.com> Message-ID: Date: Sat, 3 Sep 2016 19:44:39 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.2 MIME-Version: 1.0 In-Reply-To: <82d74255-4118-46f4-c073-35e3b224fef8@gmail.com> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] [RFC] Deprecate PEAR/PECL & Replace with composer/pickle From: lester@lsces.co.uk (Lester Caine) 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