Re: Asymmetric visibility is a BC break

From: Date: Mon, 14 Oct 2024 00:02:51 +0000
Subject: Re: Asymmetric visibility is a BC break
References: 1 2 3 4 5 6 7  Groups: php.internals 
Request: Send a blank email to internals+get-125789@lists.php.net to get a copy of this message
On Mon, 14 Oct 2024 at 01:28, Jordan LeDoux <jordan.ledoux@gmail.com>: > Backwards compatible has never, in any work I've done through my entire career, meant > something like "if you take old code and then update it to the new version incorrectly, it > doesn't work"... that seems... obvious? > > What exactly is the claim being made here? Because it sounds like the claim is very much that > second "definition". > > Jordan Hi, Jordan! 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. However, it is not compatible with PHP 8.4, I've just created an issue: https://github.com/symfony/symfony/issues/58556 The end user will be the victim, because `composer require symfony/property-info` will happily install property-info v7.1.4 for PHP 8.4, but it's not gonna work. -- Valentin

« previous php.internals (#125789) next »