Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:100899
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain kelunik.com from 81.169.146.220 cause and error)
MIME-Version: 1.0
In-Reply-To: <E3.18.07885.D0261E95@pb1.pair.com>
References: <CA+aNemZ-_L-fMdWMFf2jEo55sKWEM8C_87_hQh=LbjHBhw7Kww@mail.gmail.com>
 <E3.18.07885.D0261E95@pb1.pair.com>
Date: Sat, 14 Oct 2017 13:00:01 +0200
Message-ID: <CANUQDChnvxEG-qufFYNG7=NZNuCsH4cV_1n6UgZQNmCeFJa6+w@mail.gmail.com>
To: Andrea Faulds <ajf@ajf.me>
Cc: PHP Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="94eb2c065a58cdb74c055b7fac56"
Subject: Re: [PHP-DEV] Re: Suggestion Method Constant
From: me@kelunik.com (Niklas Keller)

--94eb2c065a58cdb74c055b7fac56
Content-Type: text/plain; charset="UTF-8"

>
> Hi Mathias,
>
>
> Mathias Grimm wrote:
>
>> I would like to suggest a method constant that could be used the same way
>> we use the ::class one
>>
>> I don't have a strong personal preference but it could be something like:
>>
>> MyController::myActionMethod::method, no sure about the internals but it
>> would be consistent with the one for the class.
>>
>> Cheers,
>>
>>
> I've long wanted to make constant lookups fall back to a closure of the
> correspondingly-named function, where one exists. so `strlen` would resolve
> to a closure of strlen().
>
> Thing is that classes are weird. We sort of have three different things
> with sometimes-similar syntax: constants, methods and properties. foo::bar
> is a constant, foo::bar() is a function, $foo->bar() is a function, but
> $foo->bar is not a constant. So, if I want $foo->bar to resolve to a
> method, then $foo::$bar should too, even though that makes no sense. The
> PHP static property syntax is the bane of my existence.


Please no fallbacks, thanks. It was already a mistake for namespaced
functions.

Regards, Niklas

--94eb2c065a58cdb74c055b7fac56--