Re: Asymmetric visibility is a BC break
| From: | Valentin Udaltsov | Date: | Mon, 14 Oct 2024 01:51:56 +0000 |
| Subject: | Re: Asymmetric visibility is a BC break | ||
| References: | 1 2 3 4 5 6 7 8 9 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-125792@lists.php.net to get a copy of this message | ||
On Mon, 14/10/2024 04:07, Bilge <bilge@scriptfusion.com> wrote:
>
> On 14/10/2024 01:02, Valentin Udaltsov wrote:
> > The problem is that in practice most of the PHP libraries consider
> > themselves to be compatible with newer PHP versions.
> >
> > For instance, Symfony PropertyInfo uses
"php":
> > ">=8.2" constraint in
> > its composer.json.
>
> That seems like a problem they have created for themselves. It seems an
> error to me to declare software forward-compatible with PHP versions
> that do not yet exist and thus have clearly not been tested against.
> Being as it is an error, we shouldn't consider it impinges on PHP's
> definition of a BC break.
>
> Cheers,
> Bilge
Hi, Bilge!
I think that PHP should then clearly explain what is a BC break and
what isn't on a separate php.net page.
And even explain what php version constraints are safe for Composer libraries.
Some languages have such a document:
- https://go.dev/doc/go1compat
- https://peps.python.org/pep-0387/
--
Valentin