Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:95601 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 48600 invoked from network); 3 Sep 2016 15:03:07 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 3 Sep 2016 15:03:07 -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:39550] helo=mail4.serversure.net) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id C9/02-32927-A26EAC75 for ; Sat, 03 Sep 2016 11:03:07 -0400 Received: (qmail 29645 invoked by uid 89); 3 Sep 2016 15:03:03 -0000 Received: by simscan 1.3.1 ppid: 29619, pid: 29640, t: 0.0730s 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 15:03:03 -0000 To: internals@lists.php.net References: Message-ID: <2e2e7a2d-4459-c59f-6552-b01314a06b2f@lsces.co.uk> Date: Sat, 3 Sep 2016 16:02:49 +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: 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 15:45, Rowan Collins wrote: > - The PEAR coding style would probably be considered "out of date" by a > lot of PHP devs. That's partly a matter of fashion, but also a natural > consequence of it predating certain language features - autoloading, > namespaces, etc - which people want to take advantage of. 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! -- 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