Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:100852
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain rhsoft.net designates 91.118.73.15 as permitted sender)
To: internals@lists.php.net
References: <9a3f15dd-5dfc-144b-cc5f-66f689c33f53@php.net>
Message-ID: <087b1ea6-240d-9e1b-52b0-947c4328aa20@rhsoft.net>
Date: Tue, 10 Oct 2017 16:03:45 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101
 Thunderbird/52.3.0
MIME-Version: 1.0
In-Reply-To: <9a3f15dd-5dfc-144b-cc5f-66f689c33f53@php.net>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: de-CH
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Strict type declarations not enforced for Reflection
 API invocation
From: lists@rhsoft.net ("lists@rhsoft.net")



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