Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:40443
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain lsces.co.uk from 213.123.20.127 cause and error)
Message-ID: <48C8073D.4050602@lsces.co.uk>
Date: Wed, 10 Sep 2008 18:43:25 +0100
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.13) Gecko/20080313 SeaMonkey/1.1.9
MIME-Version: 1.0
To: PHP internals <internals@lists.php.net>
References: <48C5F612.6090001@lsces.co.uk> <145156227.20080910184421@marcus-boerger.de>
In-Reply-To: <145156227.20080910184421@marcus-boerger.de>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] 5.3 Backwards Compatibility
From: lester@lsces.co.uk (Lester Caine)

Marcus Boerger wrote:
> Hello Lester,
>> Another major concern here since maintaining BC with *PHP4* is still an 
>> unfortunate current requirement in the field is what happens when PEAR 
>> actually uses namespace and other 5.3 only features. HOW will we manage 
>> accessing versions of PEAR that are compatible with our active codebase and so
>> ensure that we have compatible sets of packages?
> 
> PHP 4 is no longer supported - in no way. If PEAR still insists on PHP 4
> then we cannot support PEAR either. Anyway, as far as I know PEAR does a
> good job in maintenance, especially in supporting both PHP 4 and 5. And
> some people are working on a new system that supports PHP 5.

Marcus - I've never USED PHP4 in production, but it will be some time before 
it has been replaced on a lot of ISP's so at present OUR users require 
maintaining support for PHP on the only versions they have available - at 
present. NOW it at least practical to freeze a version that supports PHP4 and 
all the 'extras' that are compatible with that version and not allow any new 
features to be included in that build. SO we do not have to test changes to 
the code base for PHP5.3 against PHP4. There have always been problems with 
using 'new' features but making them available to older versions, which the 
compatibility libraries provide, but it is looking as if 'Built for PHP5.3' 
will mean 'will not work on PHP5.2' much more so than previous 'minor version 
changes'?

-- 
Lester Caine - G8HFL
-----------------------------
Contact - http://lsces.co.uk/lsces/wiki/?page=contact
L.S.Caine Electronic Services - http://lsces.co.uk
EnquirySolve - http://enquirysolve.com/
Model Engineers Digital Workshop - http://medw.co.uk//
Firebird - http://www.firebirdsql.org/index.php