Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:66667
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain pcservice.co.za designates 69.56.216.30 as permitted sender)
MIME-Version: 1.0
Reply-To: pierre@pcservice.co.za
In-Reply-To: <CACv1KMh_ahrK=bqsESzBq50KmfQxmZht-NR6Dc8acykMt1e06w@mail.gmail.com>
References: <CACv1KMh_ahrK=bqsESzBq50KmfQxmZht-NR6Dc8acykMt1e06w@mail.gmail.com>
Date: Sat, 16 Mar 2013 22:33:05 +0200
Message-ID: <CAJbumGNP=fAcQABrxa_1P1m0KcazEXp731PfSc0kHi23673xKQ@mail.gmail.com>
To: Daniele Orlando <dnl.rlnd@gmail.com>
Cc: PHP Development <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=00235429dfc4c05c0e04d810a964
Subject: Re: [PHP-DEV] __invokeStatic() method
From: pierre@pcservice.co.za (Pierre du Plessis)

--00235429dfc4c05c0e04d810a964
Content-Type: text/plain; charset=ISO-8859-1

On Mar 16, 2013 9:35 PM, "Daniele Orlando" <dnl.rlnd@gmail.com> wrote:
>
> Hi List,
>
> I'm interested in proposing an RFC and I would know your opinion.
>
> === Current Situation ===
> Since PHP 5.3 we can use an object instance, who defines the __invoke()
> method, as a callable object.
> Example:
>
> // PHP Code.
> class Runnable
> {
>     public function __invoke()
>     {
>         echo "Runned";
>     }
> }
>
> $r = new Runnable();
> $r();
>
> // Output
> Runned
>
> === The Idea ===
> In Python, when you construct an object, you don't need to use the "new"
> keyword but you just invoke the class name followed by "()", like the
class
> is a function.
> Example:
>
> // Python Code.
> class A:
>     pass
>
> A()
>
> // Output.
> <__main__.A instance at %address>
>
> Now, would be interesting to extend the PHP __invoke() method adding an
> __invokeStatic() method, like happens with __call() and __callStatic()
> methods.
> In this way could be possible to use a class name to invoke the
> __invokeStatic() method.
> Example:
>
> // PHP Code.
> class TrueRunnable
> {
>     public static function __invokeStatic()
>     {
>         echo "Runned";
>     }
> }
>
> TrueRunnable();
>
> // Output.
> Runned
>
> But the possibility are endless:
>
> class A
> {
>     public static function __invokeStatic()
>     {
>         return new A();
>     }
>     public method m() {}
> }
>
> A()->m();
>
> // or
>
> class A
> {
>     private $_instance;
>     public static function __invokeStatic()
>     {
>         // Singleton pattern.
>         if (self::$_instance) {
>             return self::$_instance;
>         }
>
>         return self::$_instance = new A();
>     }
>     public method m() {}
> }
>
> A()->m();
>
>
> === Conclusion ===
> This feature makes the __invoke() method consistent with the __call() and
> __callStatic() methods,
> and opens the door to many cool stuff.
>
> Any feedback is appreciated.
>
> Daniele Orlando

I don't really see a use case for this, as you can already use the syntax
A::method();

E.G class A { public static function invoke() { return new A; }

public function m() { echo 'Runned'; }

A::invoke()->m();

Your example above only saves a few characters to type and can lead to a
lot of problems if you have a function with the same name as the class.

--00235429dfc4c05c0e04d810a964--