Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:63804 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 12455 invoked from network); 12 Nov 2012 13:20:28 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 12 Nov 2012 13:20:28 -0000 Authentication-Results: pb1.pair.com smtp.mail=tony@daylessday.org; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=tony@daylessday.org; sender-id=unknown Received-SPF: error (pb1.pair.com: domain daylessday.org from 95.163.84.66 cause and error) X-PHP-List-Original-Sender: tony@daylessday.org X-Host-Fingerprint: 95.163.84.66 mail.daylessday.org Received: from [95.163.84.66] ([95.163.84.66:55756] helo=daylessday.org) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id FD/D0-05794-A97F0A05 for ; Mon, 12 Nov 2012 08:20:27 -0500 Received: from thinkx201.site (unknown [212.248.29.228]) by daylessday.org (Postfix) with ESMTPSA id 73CADE357D for ; Mon, 12 Nov 2012 17:20:23 +0400 (MSK) Message-ID: <50A0F797.30604@daylessday.org> Date: Mon, 12 Nov 2012 17:20:23 +0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:16.0) Gecko/20121025 Thunderbird/16.0.2 MIME-Version: 1.0 To: internals@lists.php.net References: In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] RFC: ext/mysql deprecation From: tony@daylessday.org (Antony Dovgal) On 2012-11-12 17:00, Adam Harvey wrote: > Hi everyone, > > I've written an RFC to cover deprecating ext/mysql in PHP 5.5: > https://wiki.php.net/rfc/mysql_deprecation. While we handled the soft > deprecation in the documentation purely via a straw poll on Internals, > I presume this will end up needing to go to a vote, hence the RFC. > > I won't rehash the background overly (there's some more detail in the > RFC), other than to note that we've now had deprecation notices on all > mysql_* functions in the manual for about six months and that the > logical next step is to start generating E_DEPRECATED notices when > users connect via mysql_connect(), mysql_pconnect() or the implicit > ext/mysql connection routines. While I fully understand the reasons behind this, I still believe this kind of thing should be done using the documentation only. Generating 'educational' notices will just annoy the end users and in 99% cases they can't do a thing about it - nobody's going to rewrite a large piece of legacy software just to make PHP happy. More notices doesn't necessarily mean less people are going to use ext/mysql, you can't hasten users to move if they don't really want to do it themselves. -- Wbr, Antony Dovgal --- http://pinba.org - realtime profiling for PHP