The functionality of the `__callStatic` magic method is incomplete.

[daddyofsky]

Description

The following code:

<?php
class MyClass
{
	public static function __callStatic($method, $args)
	{
		echo $method . "\n";
	}

	private function privateMethod() {}
	protected function protectedMethod() {}
	public function publicMethod() {}
}

MyClass::privateMethod();
MyClass::protectedMethod();
MyClass::publicMethod();

Resulted in this output:

privateMethod
protectedMethod
Fatal error: Uncaught Error: Non-static method MyClass::publicMethod() cannot be called statically in ...

But I expected this output instead:

privateMethod
protectedMethod
publicMethod

It seems that the __callStatic magic method is discriminating against public methods. ;)

PHP Version

PHP 8.x

Operating System

Any

[MorganLOCode]

__callStatic is used when inaccessible methods are invoked. MyClass::publicMethod() is public, hence accessible globally. __callStatic isn't being invoked.

[iluuu1994]

Right. This is consistent with the fact that two functions (static and non-static) cannot coexist, if declared directly.

[daddyofsky]

__callStatic is used when inaccessible methods are invoked. MyClass::publicMethod() is public, hence accessible globally. __callStatic isn't being invoked.

Not correct, please check manual.
__callStatic() is triggered when invoking inaccessible methods in a static context.

All dynamic methods are inaccessible in a static context.

[daddyofsky]

Right. This is consistent with the fact that two functions (static and non-static) cannot coexist, if declared directly.

In static context, public methods are inaccessible.
This is not a problem with the function declaration, but rather an issue of whether it can be used statically or not. __callStatic is intended for use when calling methods that cannot be used statically, and this should be applied to public methods as well.

[iluuu1994]

That's not how it currently works. Static and instance methods share the same symbol table. You can even call static methods as instance methods. As such, both -> and :: look up the method in the same symbol table. If found, and visibility checks succeed, the method is called (including the static-ness check). Otherwise, __call or __callStatic is called.

Your interpretation is completely reasonable, but not how it works. PHP is an implementation specified language, and any such change would require an RFC. See https://wiki.php.net/rfc/howto on how this process works.

[damianwadley]

Reminder that :: is not a "static method call operator". It is the scope resolution operator, as in it resolves what name::name means according to the current scope.

MyClass::publicMethod resolves to "the publicMethod of MyClass", which exists and is accessible. And because it exists and is accessible, __call/__callStatic will not get involved. The call is static not because of the :: but because there is no instance of MyClass in the scope to use; if there was one then it would be used and the call would not be static.
https://3v4l.org/4JV2B

[daddyofsky]

Reminder that :: is not a "static method call operator". It is the scope resolution operator, as in it resolves what name::name means according to the current scope.

MyClass::publicMethod resolves to "the publicMethod of MyClass", which exists and is accessible. And because it exists and is accessible, __call/__callStatic will not get involved. The call is static not because of the :: but because there is no instance of MyClass in the scope to use; if there was one then it would be used and the call would not be static. https://3v4l.org/4JV2B

I understand the explanation, but I believe the outcome should be the same. When a static call is made in a static context without an instance, it should invoke the __callStatic magic method if the corresponding method is not static. This would be the general expectation of those using magic methods.