Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:64094
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: <50B71568.5090101@lsces.co.uk>
Date: Thu, 29 Nov 2012 07:57:28 +0000
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20120826 Firefox/15.0 SeaMonkey/2.12
MIME-Version: 1.0
To: PHP internals <internals@lists.php.net>
References: <CADajX4BRUFUb_Wp2a40d2vwXHeMmO611Sqrv7=oxbLHag9qOyg@mail.gmail.com> <CADajX4B3RctPoodShRhLLyDQW8-QFaCBOU+6PjL0FDHPGYBtzg@mail.gmail.com> <50B5D992.30609@lsces.co.uk> <CACwt+JeuSo7TOyVLUMhvQPx2duPi9aDw=HZ=qgknKi+5kVP8VA@mail.gmail.com> <CAAyV7nGoV0Q78V6sRTNkiwsj3mZDWdJyFpDgexPe7r7B4xe8=A@mail.gmail.com> <CAKOpQSzyCjMH2Rvo4n0kgbugzvwRga4SnO4URR2uqoTefG3Z6g@mail.gmail.com> <50B6C097.5010402@gmail.com> <CAKOpQSxME1VVt4MhFxOTVhND3HW3zN0YTsbaCt8HjACUvKtaog@mail.gmail.com>
In-Reply-To: <CAKOpQSxME1VVt4MhFxOTVhND3HW3zN0YTsbaCt8HjACUvKtaog@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Re: [VOTE] ext/mysql deprecation in 5.5
From: lester@lsces.co.uk (Lester Caine)

Kris Craig wrote:
> Either way, our common goal here is to get people to stop using ext/mysql now so
> that we can trash it when the time comes.  And as far as that goes, I think that
> what happened with magic_quotes and Drupal is a perfect example of how
> deprecation can effectively push devs to act when docs and "get the word out"
> campaigns aren't enough.

The use of 'Drupal' as an example is totally spurious here. E_DEPRECATED and 
E_STRICT upgrades to any framework needed to be managed and in many cases 
switching to later versions of PHP are ALWAYS linked to a new major version of 
the framework. It is because the older versions are still expected to work with 
older versions of PHP. I'm sure you will find today that most of these 
frameworks ACTUALLY disable E_STRICT and E_DEPRECATED by default so that they 
continue to run on on the range of PHP versions they were originally designed 
for? Making something that only works with PHP5.4 is simply not practical when 
the bulk of the hosting is still on PHP5.2! Drupal is not the only framework 
that has to support it live user base.

This does return to something that people have got irritated with me before but 
has been highlighted again here. Extensions are NOT core to PHP and most 
distributions including the windows ones do not provide a single executable for 
PHP but rather allow one to select what is loaded manually. I think it is quite 
obvious that even if E_DEPRECATED gets added to an 'official' distribution of 
mysql in PHP, that this will get stripped back out by the distributions as 
inappropriate in modular distributions? So why create the agro in the first place?

It IS the education that is missing ... but equally there ARE still valid 
reasons to use mysql just as there are for the list of other retired extensions 
listed here. Creating even more problems for users is simply counter productive 
when there is STILL a need to educate users as to how to make their PHP5.2 code 
'work' with PHP5.3/4 so that ISP's ARE in a position TO upgrade at all! And I 
speak with my 'hosting' hat on here.

-- 
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
Rainbow Digital Media - http://rainbowdigitalmedia.co.uk