Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:86881
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain mabe.berlin from 80.237.132.167 cause and error)
Message-ID: <558C58E9.9010008@mabe.berlin>
Date: Thu, 25 Jun 2015 21:39:21 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0
MIME-Version: 1.0
To: Christoph Becker <cmbecker69@gmx.de>, internals@lists.php.net
References: <CAJW__o0D_DadKJCyZbMhDiEVpO-pzpWwKV5Ht=ukK1MOBCLCKg@mail.gmail.com> <558C51CA.9080905@mabe.berlin> <558C5705.9040604@gmx.de>
In-Reply-To: <558C5705.9040604@gmx.de>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Headsup: PHP7 feature freeze
From: dev@mabe.berlin (Marc Bennewitz)



On 06/25/2015 09:31 PM, Christoph Becker wrote:
> Marc Bennewitz wrote:
>
>> I would really like to see directly calling a string of "Class::method"
>> be fixed for 7.0.
>> It's currently resulting in a fatal error and is inconsistent with
>> call_user_func[_array], is_callable and the callable type-hint.
>>
>> There is also a PR open since April 2014 :
>> https://github.com/php/php-src/pull/659
> Apparently, your PR has been overlooked, but it seems this is already
> implemented as result of merging PR #1264[1]; see
> <http://3v4l.org/W8hQA>.  Can you please verify, and close your PR #659
> as appropriate.
>
> [1] <https://github.com/php/php-src/pull/1264>
>

Nice to see this - didn't noted it in the last month :)

But there is one edge case that is not handled by PHP-7 at current behavior;
http://3v4l.org/HkRQ7

class Foo {
     public static function __callStatic($m, $args) {
         var_dump($m);
     }
     public function __call($m, $args) {
         var_dump($m);
     }
}

$callable = [new Foo, ''];
$callable(); // string(0) ""

$callable = 'Foo::';
$callable(); // Fatal error: Uncaught Error: Call to undefined function 
Foo::()

This behavior is inconsistent!

Thanks
Marc