Hi,
I am open for any approach, but maybe we have to differentiate between class
constants and method references?
Michael
> Am 12.10.2017 um 20:28 schrieb Mathias Grimm <mathiasgr...@gmail.com>:
>
> The only problem with the @ symbol is the lack of consistency with the other
> constants class constants are also MyClass::MY_CONST, or MyClass::class, so I
> think it makes sense to also be MyClass::myMethod::method
>
>> On 12 October 2017 at 20:24, Michael Döhler <michaeldoeh...@me.com> wrote:
>> Hi,
>>
>> Same i have in mind, for example: MyClass@myMethod
>>
>> To make also some method call routing easier, e.g. in userland routers.
>>
>> Transform the current approach:
>>
>> $app->get("/foo", [MyClass::class, "myMethod"]);
>>
>> To:
>>
>> $app->get("/foo", MyClass@myMethod);
>>
>> This will ease a lot, e.g. for refactoring, IDE usage and completes the code
>> as configuration approach for PHP.
>>
>> Thanks
>> Michael
>>
>> > Am 12.10.2017 um 19:43 schrieb Mathias Grimm <mathiasgr...@gmail.com>:
>> >
>> > 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,
>
