Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:82209 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 11530 invoked from network); 9 Feb 2015 01:31:48 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 9 Feb 2015 01:31:48 -0000 Authentication-Results: pb1.pair.com header.from=lester@lsces.co.uk; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=lester@lsces.co.uk; spf=permerror; 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:57521] helo=mail4.serversure.net) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 63/F0-26926-20E08D45 for ; Sun, 08 Feb 2015 20:31:47 -0500 Received: (qmail 2318 invoked by uid 89); 9 Feb 2015 01:31:44 -0000 Received: by simscan 1.3.1 ppid: 2312, pid: 2315, t: 0.0788s scanners: attach: 1.3.1 clamav: 0.96/m:52/d:10677 Received: from unknown (HELO ?10.0.0.8?) (lester@rainbowdigitalmedia.org.uk@86.189.147.37) by mail4.serversure.net with ESMTPA; 9 Feb 2015 01:31:43 -0000 Message-ID: <54D80DFF.6090005@lsces.co.uk> Date: Mon, 09 Feb 2015 01:31:43 +0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: internals@lists.php.net References: <54D606D2.7030102@lsces.co.uk> <54D74BFF.3070604@b1-systems.de> <54D756D4.20006@lsces.co.uk> <54D7B267.5000902@gmail.com> <54D7CCB5.2020709@lsces.co.uk> <54D7F9BD.9080407@gmail.com> In-Reply-To: <54D7F9BD.9080407@gmail.com> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] Dragging the legacy users forward. From: lester@lsces.co.uk (Lester Caine) On 09/02/15 00:05, Rowan Collins wrote: >> Some of the new 'styles' of writing things are >> going to make things considerably worse for those who are going to have >> to maintain this code in the future. > > If you're writing code that you know will be hard to maintain in the > future, you're doing something wrong. If by slavishly following a style > guide you've ended up with a poor architecture, you need a better style > guide, or a better understanding of why those styles are preferred. > > Alternatively, I may have misunderstood that sentence, in which case I > apologise in advance. Something *I* have been asking for for the last few years IS a better 'style guide' ... There are a growing number of 'styles' and the current debate is to allow even more! Just about every framework has a different style of handling database abstraction, and that seems to change every major version as well. All of my own code is based around ADOdb, but now it seems THAT is not an acceptable style of code these days. Anyway I now have PHP56.lsces.org.uk running with the latest PHP5. It's throwing megabytes of data into the error log but there ACTUALLY seem to be less in the php7 error log ... need to figure that out, but I've currently hit the latest brick wall as mbstring is not compiling! Most of the others have compiled fine, but currently there is a blank front page until I can work out what is going wrong ... that and smarty is throwing errors ... -- 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