Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:127806
Precedence: bulk
MIME-Version: 1.0
References: <CA+NMNO0K85acCismdBL=8vr5=nKg1_-i0BjXyiqnjoqGAnH3Xw@mail.gmail.com>
 <CANLbj-ppn+QtYij2uHXmNvbXckKzz84fkj6f-6iw_7wioFN0dA@mail.gmail.com> <CAOWwgpnPMw8LsT6+0bQgM13-8DpsaKwxM4dpGxDSv_ihNMB+cw@mail.gmail.com>
In-Reply-To: <CAOWwgpnPMw8LsT6+0bQgM13-8DpsaKwxM4dpGxDSv_ihNMB+cw@mail.gmail.com>
Reply-To: erictnorris@gmail.com
Date: Mon, 30 Jun 2025 11:37:10 -0400
Message-ID: <CA+NMNO1ck3k872=Q8OwD2hGDJsFfkPr5A_EioTLBZZ0z8XbpBw@mail.gmail.com>
Subject: Re: [PHP-DEV] [RFC][DISCUSSION] Object-oriented curl API v2
To: Nicolas Grekas <nicolas.grekas+php@gmail.com>
Cc: Ayesh Karunaratne <ayesh@php.watch>, PHP internals <internals@lists.php.net>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
From: eric.t.norris@gmail.com (Eric Norris)

> I'm not even sure it's a good idea to add those namespaced options: using=
 CURLOPT_SSL_VERIFYHOST is perfect to find the corresponding curl documenta=
tion with your favorite search engine. php's doc is awesome, but it cannot =
compete with the details provided by curl's doc on the topic.

That's a good point, but I do feel like there is value in having these
under a namespace; a part of the reason I am interested in this
proposal is that I'd like to see more of PHP core living under
namespaces, since I think it will present a more consistent vision of
the "standard library". I wonder if there is a way we could preserve
the link, at least? In my proposal, the enum values are equivalent to
their curl constant equivalents, which I thought would help with
discoverability in the documentation.

For the record - and I'll say this elsewhere - based on the discussion
so far I am planning on withdrawing the proposal for separate enums.
I'm still considering using a single enum to group all of these
options, however, instead of constants.