Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:83623 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 70510 invoked from network); 23 Feb 2015 23:12:59 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 23 Feb 2015 23:12:59 -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:59167] helo=mail4.serversure.net) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id FF/E1-61054-9F3BBE45 for ; Mon, 23 Feb 2015 18:12:58 -0500 Received: (qmail 16948 invoked by uid 89); 23 Feb 2015 23:12:54 -0000 Received: by simscan 1.3.1 ppid: 16939, pid: 16942, t: 0.0821s 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; 23 Feb 2015 23:12:54 -0000 Message-ID: <54EBB3F6.7020605@lsces.co.uk> Date: Mon, 23 Feb 2015 23:12:54 +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: <7ef509ef10bb345c792f9d259c7a3fbb@mail.gmail.com> <9aec85c81b49009c6238ff6d8be27cd4@mail.gmail.com> <2dcfd9f4a3f0f9bbf2a13f679359e6ea@mail.gmail.com> <6844321d7134506b1061c5f18a275069@mail.gmail.com> In-Reply-To: <6844321d7134506b1061c5f18a275069@mail.gmail.com> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] Coercive Scalar Type Hints RFC From: lester@lsces.co.uk (Lester Caine) On 23/02/15 20:57, Zeev Suraski wrote: > They don't upgrade even when there's > no or very little compatibility breakage. That's why 5.3 is still so > popular, and 5.2 isn't rare to find. Let alone 5.4. You know my position here but not only are the problems of areas that were deprecated in 5.3 and removed in 5.4, trying to provide a hosted version of PHP that works for the older code while keeping the 5.4+ code happy is a problem. I've just been hit with a change of ownership of one of my legacy services and the new owner has 'upgraded' resulting in several sites now having problems. Yes they run but not clean and out of 8 sites I've acquired 5 completely different frameworks. Add in a change from Apache to Nginx ... you get the picture ... I've moved them all to one of my own machines with a 'compatible' build of PHP and we are working again. Should I have reworked each to get them running, yes, but which customer do you keep happy first? They WILL all be moved to a single modern framework ... and I've been saying that since 2012 ... but at least finally I HAVE a stable system on 5.4 which does seem to work with 5.6 and also with the current PHP7 build. However in the process I've lost eaccelerator which used to work well on the PHP5.2 hosting, so I need an alternative simply to stand still ... and while PHP7 is giving a speed improvement it still lags behind what I have on the PHP5.4 machines with eaccelerator. So first step get up to the same platform with all sites, but currently there is no incentive to switch to a slower system ... Your speed table from earlier shows a marked improvement up to PHP5.4 with eaccelerator loaded. PHP7 reduces memory usage and execution time against a basic PHP5.x but not against my PHP5.4/eaccelerator base ... -- 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