Re: Re: Inaccurate documentation on return values from native functions
| From: | Hans Henrik Bergan | Date: | Sun, 01 Dec 2024 20:32:29 +0000 |
| Subject: | Re: Re: Inaccurate documentation on return values from native functions | ||
| References: | 1 2 3 4 5 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-126090@lists.php.net to get a copy of this message | ||
On Sun, Dec 1, 2024, 20:12 Christoph M. Becker <cmbecker69@gmx.de> wrote:
> On 01.12.2024 at 19:26, mickmackusa wrote:
>
> > On Sun, Dec 1, 2024 at 10:01 PM Gina P. Banyard <internals@gpb.moe>
> wrote:
> >
> >> This should just have been an issue on the php/doc-en repo.
> >>
> >> Please open such an issue so that we can track it (or submit a PR).
> >
> > I am not sure that this is purely a problem with the documentation.
> > It seems possible to me that someone updated the documentation to
> reflect a
> > new intention for these functions.
> > Will it not be that these functions will be altered in the core to do
> what
> > the documentation says?
>
> If the docs are not correct, we cannot simply change the source to
> conform for BC reasons.
>
> In this case, see
> <https://github.com/php/doc-en/issues/3629>.
>
> Christoph
>
The same way we can't simply stop curl_close from writing to
CURLOPT_COOKIEFILE for BC reasons? (
https://github.com/php/doc-en/issues/2239 )
>