> 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 > documentation 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.
