Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:63829 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 32603 invoked from network); 13 Nov 2012 03:14:02 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 13 Nov 2012 03:14:02 -0000 Authentication-Results: pb1.pair.com header.from=adam@adamharvey.name; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=adam@adamharvey.name; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain adamharvey.name designates 209.85.219.42 as permitted sender) X-PHP-List-Original-Sender: adam@adamharvey.name X-Host-Fingerprint: 209.85.219.42 mail-oa0-f42.google.com Received: from [209.85.219.42] ([209.85.219.42:48680] helo=mail-oa0-f42.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 56/B3-05346-7FAB1A05 for ; Mon, 12 Nov 2012 22:13:59 -0500 Received: by mail-oa0-f42.google.com with SMTP id j1so7228105oag.29 for ; Mon, 12 Nov 2012 19:13:56 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=adamharvey.name; s=google; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type :content-transfer-encoding; bh=ySTVM54UUK6XodYjwVMzSev7y/G4OsLfDXJNXG3E6l8=; b=B24v67y/BaiDftgYOzidgLd7rPFU10M5mAO2fL6pI1q/s9wA8hG27kDMucoaDIFtpe CXA71NRCVNmrEp79kxWO4JdLnDL0XAORQ17SoNDI8WAARAVa9nzJwkOOvT5Z81UM+yf+ VaZHx+FqvlpZtGo9wRwMymt/N01h4wRNYhgdQ= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type :content-transfer-encoding:x-gm-message-state; bh=ySTVM54UUK6XodYjwVMzSev7y/G4OsLfDXJNXG3E6l8=; b=SnJ7MvdQLCLhOP9zwJzhSx8YmlimukroQsnZxtycFlYWGG1dfkV/S3BXh9RqgUWuBS dNtymGvzMyFpYwtEJ7X0s8vhi4iIAzuSoA2Osjg6ChbswKGfWq2Hrqdm/a18KMmVtoiB Md8iQ7d+FC1Qg9o9thloUjvMt14TTzKCiktWWUrhUumAxnTiO+MWx3QwM9nGZEN043qO +ES2nkfkXCx7eW1FK18ZEqGytU9J7Vz7H8EJCYwWcBijYvJ7q9/9muw/kdixDnSD/3bB 9cCSEx9XpxXSR5o+G2exazLLGopLUkwkmosEzkxQs4i8e9JLihChXyeetQfefIRBSKPv ofQA== Received: by 10.182.146.46 with SMTP id sz14mr16720739obb.76.1352776436829; Mon, 12 Nov 2012 19:13:56 -0800 (PST) MIME-Version: 1.0 Sender: adam@adamharvey.name Received: by 10.76.123.75 with HTTP; Mon, 12 Nov 2012 19:13:36 -0800 (PST) In-Reply-To: References: <50A0F797.30604@daylessday.org> <50A10C43.2000704@daylessday.org> <50A10EF1.1010405@oracle.com> Date: Tue, 13 Nov 2012 11:13:36 +0800 X-Google-Sender-Auth: IC-tffrrsOTij39Z3U2hyZoULcE Message-ID: To: Ferenc Kovacs Cc: Ulf Wendel , PHP Internals Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Gm-Message-State: ALoCoQkJQkrp4vDyPLfSOcKj7r6Gu4kLAOPssXzCmsuE4SNcsj6oc1DrfUIK1V5/K8mqN5rOPd9Y Subject: Re: [PHP-DEV] RFC: ext/mysql deprecation From: aharvey@php.net (Adam Harvey) On 13 November 2012 01:16, Ferenc Kovacs wrote: > On Mon, Nov 12, 2012 at 4:00 PM, Ulf Wendel wrote= : >> Don't bother. There is a standard way of deprecation, at least I assume >> there is. Its proven. Use it: docs warnings, E_DEPRECATED, remove. > > I agree to deprecate/remove on the long run, but I think that we should > wait for the next version for doing so. Honestly, if we were going to delay the eventual removal (and I'm not sure we should), I'd rather have an extra release cycle with E_DEPRECATED, rather than an extra release cycle with documentation-only warnings that are more easily ignored =E2=80=94 so eithe= r way, I'd still want the notices in 5.5. Adam