Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:63914 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 99379 invoked from network); 16 Nov 2012 08:58:18 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 16 Nov 2012 08:58:18 -0000 Authentication-Results: pb1.pair.com smtp.mail=lang@b1-systems.de; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=lang@b1-systems.de; sender-id=unknown Received-SPF: error (pb1.pair.com: domain b1-systems.de from 217.11.58.35 cause and error) X-PHP-List-Original-Sender: lang@b1-systems.de X-Host-Fingerprint: 217.11.58.35 mx1.b1-systems.de Linux 2.6 Received: from [217.11.58.35] ([217.11.58.35:39696] helo=mx1.b1-systems.de) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id D3/55-63561-72006A05 for ; Fri, 16 Nov 2012 03:58:16 -0500 Received: from RLT400ETH.fritz.box (p54B00552.dip0.t-ipconnect.de [84.176.5.82]) by mx1.b1-systems.de (Postfix) with ESMTPSA id DA2184075 for ; Fri, 16 Nov 2012 09:58:12 +0100 (CET) Message-ID: <50A60024.5070608@b1-systems.de> Date: Fri, 16 Nov 2012 09:58:12 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:14.0) Gecko/20120713 Thunderbird/14.0 MIME-Version: 1.0 To: internals@lists.php.net References: <50A1946F.8010407@lerdorf.com> <50A20CCB.8090909@lsces.co.uk> <8A8A29F9E43E417FB5450D63019B2DDB@NeiRoze> <8f4231fc-6e3c-4a33-af71-2af5e7a95dfd@email.android.com> <50A2D672.7010600@gmail.com> <50A30144.5070305@phpgangsta.de> <50A3BEC0.8030607@gmail.com> <50A54713.8090102@sugarcrm.com> <50A549EB.2020408@lerdorf.com> <50A5FB0C.1080602@lerdorf.com> In-Reply-To: <50A5FB0C.1080602@lerdorf.com> X-Enigmail-Version: 1.4.4 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig422573EA0B203189347864ED" Subject: Re: [PHP-DEV] RFC: ext/mysql deprecation From: lang@b1-systems.de (Ralf Lang) --------------enig422573EA0B203189347864ED Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable > Actually we have never used E_DEPRECATED to deprecate an entire > extension. We have deprecated specific functions and engine features, > but for entire extensions we have provided alternatives and/or waited > for them to become inconsequential and then moved them to pecl. But we > certainly never littered the extension with warnings before moving it o= ut. >=20 > How do you see adding E_DEPRECATED working here? Do we add it to every > function in the extension? Just to some? And then when we move the > extension to pecl do we pull the warnings back out? Surely it makes no > sense to move an extension out of core to pecl and spew E_DEPRECATED > warnings to people who explicitly choose to install it. >=20 > -Rasmus >=20 Would it work to somehow have a pecl extension override the core-shipped extension? mysql did this when they allowed an external implementation of InnoDB to replace the InnoDB shipped with the product. This would allow turning off mysql deprecation warnings for those who know what they are doing and provide a migration path. --=20 Ralf Lang Linux Consultant / Developer Tel.: +49-170-6381563 Mail: lang@b1-systems.de B1 Systems GmbH Osterfeldstra=DFe 7 / 85088 Vohburg / http://www.b1-systems.de GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537 --------------enig422573EA0B203189347864ED Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ iEUEARECAAYFAlCmACQACgkQCs1dsHJ/X7CPAgCg4NnnuH7UT04y01Uvbv1uNsWo P04Al3Qh3ad5pY6yO/CQ97pj4Hn7GpM= =4S00 -----END PGP SIGNATURE----- --------------enig422573EA0B203189347864ED--