Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:47388
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.131 cause and error)
Message-ID: <4BA1D4B1.20707@lsces.co.uk>
Date: Thu, 18 Mar 2010 07:22:25 +0000
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.8) Gecko/20100217 Fedora/2.0.3-1.fc12 SeaMonkey/2.0.3
MIME-Version: 1.0
To: PHP Developers Mailing List <internals@lists.php.net>
References: <4B9926E8.4080202@lerdorf.com> <alpine.DEB.2.00.1003131123540.4153@kossu.derickrethans.nl> <dc2522541003131015k7f38c733i21b128529b578d3f@mail.gmail.com> <698DE66518E7CA45812BD18E807866CE03ECF62E@us-ex1.zend.net>
In-Reply-To: <698DE66518E7CA45812BD18E807866CE03ECF62E@us-ex1.zend.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] PHP 6
From: lester@lsces.co.uk (Lester Caine)

Andi Gutmans wrote:
>> We need to focus on Unicode more than what some says, whether this
>> means descoping the Unicode release or not. However, this means that
> the
>> development focus needs to be towards new features AND Unicode, not
>> having the new feature branch, and the siberia branch with Unicode
> support.
>
> I think the key to rebuilding momentum in PHP development is to not try
> and boil the ocean but to focus on "smaller" major releases. This would
> enable us to manage a more predictable release cycle, lower the risk for
> each release incl. better manage compatibility and increase motivation
> for contributors as they know they can have an impact and if they can't
> make one release they know the next isn't that far off (the latter also
> eliminates pressure to push pre-mature functionality into a release).

Please can we also put PDO back in the melting pot ... this is also still a 
'pre-mature' functionality partly because of the very limited target it set, but 
this has also resulted in a base that simply does not work. All of the database 
drivers are getting new features which SHOULD be developed at the PDO level if 
THAT is to become the standard. At present no one is working on the gaps in PDO 
mainly because adding database specific features can't be handled, and therefore 
projects that have switched to PDO are finding that even for MySQl and Posgresql 
( the only two drivers that are reasonably stable in PDO ) they have to also 
access the native drivers ...

The base class for PDO simply does not allow any chance of supporting cross 
connection activities - something which is rather important as projects scale.

-- 
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//
Firebird - http://www.firebirdsql.org/index.php