Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:81074
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.178 as permitted sender)
User-Agent: K-9 Mail for Android
In-Reply-To: <54C2E405.4090204@gmail.com>
References: <54BEC072.5000507@mabe.berlin> <CAF+90c97pHH7+qnxV61RjTRv3-vOzHn9oGva3wHVGgbMEE=aSw@mail.gmail.com> <AAD87184-07B2-4E93-B872-1F2587CA9260@ajf.me> <54C28B63.1040506@gmail.com> <54C2E405.4090204@gmail.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Content-Type: text/plain;
 charset=UTF-8
Date: Sat, 24 Jan 2015 14:24:56 +0000
To: Stanislav Malyshev <smalyshev@gmail.com>,internals@lists.php.net
Message-ID: <A89BD51A-C383-4837-AADF-7FFED75374DC@gmail.com>
Subject: Re: [PHP-DEV] Inconsistencies in callable, call_user_func and direct variable calls
From: rowan.collins@gmail.com (Rowan Collins)

On 24 January 2015 00:15:01 GMT, Stanislav Malyshev <smalyshev@gmail.com> wrote:
>Hi!
>
>> Foo::bar(); // OK
>> ['Foo', 'bar'](); // OK
>> 'Foo::bar'(); // FATAL ERROR
>
>I'm not sure why one would ever need/want the latter. IMO, it just
>looks
>weird.

Well, they both look weird as literals like that, but the array looks the wierder of the two to me. Representing a static call in some external configuration is an example where a single string in normal PHP syntax would make more sense than needing to create a 2-element array.