I suppose this isn't a bug since PHP 5 inherits classes public static methods too (and they call them ... feature ... ).

$r->invoke(new MyClass, array());

This should be expected bahaviour or there's something wrong on this "bogus": http://bugs.php.net/bug.php?id=40886

If this bug will be solved, PHP developers should think about *difference* between public static methods and instances methods, that are two different things, expecially without overload possibility changing arguments or using __call too, that in this case, isn't "so magic", IMHO.

If anybody needs invokeArgs functionality though the following code works fine:

<?
class A
{
	public static function run()
	{
		$class = new ReflectionClass('B');
		$method = $class->getMethod('foo');
		call_user_func_array(array($method, 'invoke'), array('B', 1, 2));
	}
}

class B extends A
{
	public static function foo($v1, $v2)
	{
		echo $v1." / ".$v2;
	}
}

B::run();

Expected result:
----------------
1 / 2

Actual result:
--------------
1 / 2

> Currently, ReflectionMethod::invoke() can be called using a
> string class name as the first argument *if* the method is
> declared static.

Actually, the first parameter to ReflectionMethod::invoke() is
completely ignored, if the method is a static method, see
<https://3v4l.org/e9h1S>. A comment in the sources[1] also
explains the reasoning.

This doesn't make any sense, however, because for static methods
to be invoked, NULL is supposed to be passed as first parameter to
::invoke() as well as ::invokeArgs(). Allowing an arbitrary
argument is confusing at best.

Changing the behavior would introduce a BC break, though, so it
appears to be reasonable to do that for PHP 7.1 only.

[1] <https://github.com/php/php-src/blob/PHP-7.0.10/ext/reflection/php_reflection.c#L3197-L3202>

This request has been implemented with
<http://git.php.net/?p=php-src.git;a=commit;h=f706897f330038d17570f5d0e6091e06d90179a6>.