Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:40425
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.119 cause and error)
Message-ID: <48C773B3.106@lsces.co.uk>
Date: Wed, 10 Sep 2008 08:13:55 +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> <48C60671.4040608@chiaraquartet.net> <48C6120E.6020606@lsces.co.uk> <112381E8-25B5-4968-8E93-B3B7C7152E8C@pooteeweet.org>
In-Reply-To: <112381E8-25B5-4968-8E93-B3B7C7152E8C@pooteeweet.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Re: 5.3 Backwards Compatibility
From: lester@lsces.co.uk (Lester Caine)

Lukas Kahwe Smith wrote:
> Hi,
> 
> So let me get this straight, you are complaining that all the new 
> features and changes in the 5.3.0 alpha releases are not perfectly 
> documented yet?

PLEASE re-read the original post.
If my comments and QUESTIONS are taken as complaints then OK. That is not what 
was intended.
searching on 'namespace' was not giving me anything - I did not think to try 
'namespaces' - goto has not got any notes yet? - I've not even looked at phar 
as it's not on the list I gave the link for so I assume it's still an optional 
PECL package ...

The 'complaint' that I have is that the changes being introduced DO seem to be 
bringing in problems which when corrected for 5.3 then cause other problems 
for previous versions of PHP. As an example, the bitweaver framework currently 
runs out of the box on PHP4 and PHP5. RUNNING it on PHP5.3 gives various 
warnings and errors that handling for 5.3 then messes up previous versions 
although WHEN migration is documented there may be options provided that solve 
those problems?
( And PEAR comes into this equation since potentially we may have to take care 
of pre and post 5.3 situations? )
Hanging fixes through the code with 'version selects' has not been necessary 
much up to now but 5.3 seems to be heading that way? We are currently working 
through the bitweaver 2.1 testing, on 5.2.6 and below so have not yet had time 
to do any more than checking the code runs on 5.3. The list of things to be 
looked at on 5.3 was growing so has had to be shelved until the next bitweaver 
release is out. One has to allocate time productively and BW is currently 
paying the mortgage for me!

-- 
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