Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:40428
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.200.170 as permitted sender)
DomainKey-Status: bad
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version
         :content-type:content-transfer-encoding:content-disposition
         :references:x-google-sender-auth;
        b=VySgZ3iGlDauoinJEpBrBo13V/0RMrHq1QKxxJcIe4j82X59UcUUQY5s7z6zAB5aUa
         FFZ8BK4l4IByycUclJUvBqCaonHzXpYxJQm1jsvLBDxW9bq08r9Bfvjl5NbFAtvfp4ZE
         MtTnUAPhcbLtLommBOPT2OZzlPN+bYBa3Qj38=
Message-ID: <b5f7bf6c0809100034w12bd6976ka7b9c6dd019f238d@mail.gmail.com>
Date: Wed, 10 Sep 2008 08:34:45 +0100
Sender: david.coallier@gmail.com
To: "Lester Caine" <lester@lsces.co.uk>
Cc: "PHP internals" <internals@lists.php.net>
In-Reply-To: <48C773B3.106@lsces.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <48C5F612.6090001@lsces.co.uk> <48C60671.4040608@chiaraquartet.net>
	 <48C6120E.6020606@lsces.co.uk>
	 <112381E8-25B5-4968-8E93-B3B7C7152E8C@pooteeweet.org>
	 <48C773B3.106@lsces.co.uk>
Subject: Re: [PHP-DEV] Re: 5.3 Backwards Compatibility
From: davidc@php.net ("David Coallier")

2008/9/10 Lester Caine <lester@lsces.co.uk>:
> 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, if you have more complaints or suggestions regarding PEAR, I
would like to ask you to go on pear-dev. We'll be happy to help you
resolve the situations or work something out. Many developers there
are running 5.3 as testers and we have had all the problems.

Thank you very much,

-- 
Slan,
David