Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:82133
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Message-ID: <14.24.24707.48937D45@pb1.pair.com>
To: internals@lists.php.net
References: <54D606D2.7030102@lsces.co.uk> <CAGa2bXbA8fMRi9jNj62b1Tx+-eAJtUkr2T3V_RD9Us+sLWVW3w@mail.gmail.com> <54D73248.9030509@lsces.co.uk>
In-Reply-To: <54D73248.9030509@lsces.co.uk>
Date: Sun, 8 Feb 2015 10:24:58 -0000
Lines: 1
MIME-Version: 1.0
Content-Type: text/plain;
	format=flowed;
	charset="utf-8";
	reply-type=original
Content-Transfer-Encoding: 7bit
Importance: Normal
Subject: Re: [PHP-DEV] Dragging the legacy users forward.
From: TonyMarston@hotmail.com ("Tony Marston")

"Lester Caine"  wrote in message news:54D73248.9030509@lsces.co.uk...
>
>On 08/02/15 06:37, Yasuo Ohgaki wrote:
>> Hi Lester,
>>
>>     PHP7 is proposing a LOT of shiny new features which will break much
>>     legacy code. So the question has to be just what is the plan 
>> regarding
>>     cross version support. I see that the general consensus is PHP5 
>> should
>>     just run?
>>
>> Do you mean release 5.7 or extend life of 5.6?
>> I'm +1 for both options.
>> Extending 5.6 life may achieved consensus.
>> Perhaps, 2 year security support?
>
>Well I don't remember any such restriction on PHP4? Although there is
>still a compatibility library to emulate some later features where PHP4
>did not provide them. But we are only talking about 'PHP4' being stable
>up to PHP5.2 and quoting periods here is irrelevant. Nobody is currently
>taking any notice of the fact HP5.2 and 5.3 are no longer supported and
>it's that the removal of features was badly managed that has created
>this problem.
>
>From a day to day survival point of view I have to decide what to do
>with currently functional sites that ARE still on PHP5.2 hosting. The
>bulk of the sites that have been moved to PHP5.4 still require regular
>work because people keep finding fault with one mobile device or another
>not displaying 'bootstrap3' properly which is another major upgrade path
>that is the MAIN reason for reworking sites and the one that prevents
>simple sticking plasters to hack PHP changes.
>
>I spent most of yesterday trying to get a key component of a financial
>site into a format that it could even be used on a mobile phone. And
>failed, so now I have to find another way to meet the LEGAL requirement
>that the customer has to comply with.
>
>So in general no I'm not talking about having to fix PHP5 code to some
>PHP7 compliant state, I AM talking about current PHP5 code simply
>working as PHP4 did into PHP5 hosting! CURRENTLY my php7 test site is
>running PHP5.4 live code so I don't think I'm out of line here, but if
>something goes in which causes my php7 test site to crash then I would
>prefer that to be sorted by PHP7 rather than having to upgrade to some
>as yet unavailable PHP5.x, although I would be more than happy if I can
>simply amend the live code and make both work.
>

Well said. If it is not possible to have a single codebase that runs in both 
PHP 5 *AND* PHP 7 then that will be a total disaster.

-- 
Tony Marston