Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:119429
Feedback-ID: i8414410d:Fastmail
User-Agent: Cyrus-JMAP/3.9.0-alpha0-85-gd6d859e0cf-fm-20230116.001-gd6d859e0
Mime-Version: 1.0
Message-ID: <93916c5b-6fc6-43a9-8415-5e5b0cdfaa8f@app.fastmail.com>
In-Reply-To: <3bebd28c-ebaf-53ab-5f2e-42893bc596bf@gmx.de>
References: <f90d3a56-a832-7d42-38c0-22ecd4c26901@heigl.org>
 <ba0844cb-48e0-452a-a390-069fe3a069da@app.fastmail.com>
 <CAAKU0uk7H8fZmwFEzV5Hm+kWvBZVK2ASz5KYZXBowVN=4GuC5g@mail.gmail.com>
 <3bebd28c-ebaf-53ab-5f2e-42893bc596bf@gmx.de>
Date: Fri, 27 Jan 2023 10:34:42 -0600
To: "php internals" <internals@lists.php.net>
Content-Type: text/plain
Subject: Re: [PHP-DEV] Deprecate ldap_connect with host and port as separate arguments
From: larry@garfieldtech.com ("Larry Garfield")

On Fri, Jan 27, 2023, at 10:28 AM, Christoph M. Becker wrote:
> On 27.01.2023 at 17:06, Levi Morrison via internals wrote:
>
>> On Fri, Jan 27, 2023 at 8:54 AM Larry Garfield <larry@garfieldtech.com> wrote:
>>>
>>> On Fri, Jan 27, 2023, at 3:00 AM, Andreas Heigl wrote:
>>>
>>>> I think it would be a good idea to deprecate calling ldap_connect with 2
>>>> parameters host and port.
>>>
>>> This would require an RFC, obviously, but it seems reasonable to me.  "Variable meaning parameters" was always a bad idea, and cleaning them up is a good idea.>
>> I disagree that this needs an RFC. The docs have long-said it's
>> deprecated; adding a deprecation message _in code_ to match shouldn't
>> require an RFC.
>
> In my opinion, a dedicated RFC would be overkill, but it could be added
> to the deprecations for PHP 8.3 RFC[1] what doesn't require much effort
> (feel free to add it, Andreas), and this way there would be more
> visibility, and we have a vote.
>
> [1] <https://wiki.php.net/rfc/deprecations_php_8_3>

That makes sense to me.

--Larry Garfield