Re: Strict type declarations not enforced for Reflection API invocation

Am 10.10.2017 um 15:41 schrieb Sebastian Bergmann:

https://bugs.php.net/bug.php?id=75345 is about the fact that strict type declarations are not enforced when a function or method is invoked via the Reflection API. There is a pull request that addresses this (as well as https://bugs.php.net/bug.php?id=74750) at https://github.com/php/php-src/pull/2837. I consider this a serious bug that leads to unexpected, confusing problems such as https://github.com/sebastianbergmann/phpunit/issues/2796#issuecomment-335180273. I understand Nikita's point of view (see https://github.com/php/php-src/pull/2837#issuecomment-335405067) that changing this behavior (aka. fixing this bug) can be considered a "non-trivial backwards compatibility break". Therefore I would like to bring this issue to the attention of this list with this mail

i don't see the argument of "non-trivial backwards compatibility break" in case of a major bug - which code should break? the one rely on broken bahvior? that code is already broken in in such cases it should raise errors as soon as possible instead get extended and then years later when the wrong behavior si fixed the breakage and work to fix bad code relying on the old one is even greater to say it in other words: if i have written code that relys on wrong behavior i would like to know it yesterday and fix it tomorrow instead that i continue to exnted and write such code and that with 7.3 or so i have magnitudes more to change and adopt