Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:113800
To: Nikita Popov <nikita.ppv@gmail.com>,
 PHP internals <internals@lists.php.net>
References: <CAF+90c9crhPpSMcTx-ozGo0LGjNuBU43e8fiK_=PJMU6iTHNmw@mail.gmail.com>
Message-ID: <7960f1c9-2f72-f923-47db-91dbc0a99b5a@gmx.de>
Date: Fri, 26 Mar 2021 15:41:53 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101
 Thunderbird/78.8.1
MIME-Version: 1.0
In-Reply-To: <CAF+90c9crhPpSMcTx-ozGo0LGjNuBU43e8fiK_=PJMU6iTHNmw@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Language: de-DE
Content-Transfer-Encoding: quoted-printable
Subject: Re: [RFC] Deprecations for PHP 8.1
From: cmbecker69@gmx.de ("Christoph M. Becker")

On 22.03.2021 at 10:24, Nikita Popov wrote:

> It's time for another deprecation RFC:
> https://wiki.php.net/rfc/deprecations_php_8_1
>
> As we're still early in the release cycle, it's still possible to add
> additional deprecation candidates, given reasoning for the deprecation, =
as
> well as available alternatives.

I'd like to propose the deprecation of odbc_result_all()[1].  My main
motivation for getting rid of this function is to reduce unnecessary
complexity in the ODBC extension.  I doubt that this function is used
(often) in production code, and even for quick experiments/tests it is
unlikely to be helpful.  For those needing it, it shouldn't be hard to
implement it in PHP.

[1] <https://www.php.net/manual/en/function.odbc-result-all.php>

=2D-
Christoph M. Becker