Re: [PHP-DEV] Suggestion Method Constant
On 12/10/2017 22:32, Sara Golemon wrote: answer, but (Foo::class.'::bar') may be what some would expect. Ideally we'd have first-class references to functions. -Sara To chime in.. To my mind, references to functions is the holy grail so far as beginning to clean up the entire ecosystem around function calls. IMHO directly referencing MyClass::StaticFunction eventually needs to return a "Function" class that is directly invokable. I see 3 contexts that the parser would need to handle: 1. Standard Calling MyClass::StaticFunction(1, 2, 3); my_function(1, 2, 3) $inst->my_function(1234); Obviously returning a full function object to useland for every call would be considered wasteful, so the parser would need to call these as before. 2. Returning a native "Function" class, an __invokeable hybrid of Callable and Reflection; $method = MyClass::StaticFunction; $method(1, 2, 3); $method = $inst->my_function; /* bind to $inst */ $method(1, 2, 3); $method->getName(); $method->getArgumentCount(); $method->getBinding(); 3. Returning closures when the argument list includes one or more late-bound values, so we can finally put the pipe operator to bed at the same time as getting a bunch of other power from it. $method = MyClass::StaticFunction($1, 'Arg 1', 'Arg 3); $method('Arg 1'); $method = $inst->my_function('Arg 1', 'Arg 2', $1); $method('Arg 3'); chain( 'Random String', func_1($1, 'Hello', 'World'), func_2($1, 'Peace', 'Out'), func_3('ThisOneNeeds', 'Arg3ReplacingInstead', $1), func_3($1, $1, 'HowAboutOneWhichUsesTheSameArgumentTwice') ); function chain($start, ... $fns) { foreach ($fns as $fncall) { $start = $fncall($start); } return $start; } -- Mark Randall -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] Suggestion Method Constant
On 12/10/2017 22:32, Sara Golemon wrote: > Ideally we'd have first-class references to functions. > -Sara To chime in.. To my mind, references to functions is the holy grail so far as beginning to clean up the entire ecosystem around function calls. IMHO directly referencing MyClass::StaticFunction eventually needs to return a "Function" class that is directly invokable. I see 3 contexts that the parser would need to handle: 1. Standard Calling MyClass::StaticFunction(1, 2, 3); my_function(1, 2, 3) $inst->my_function(1234); Obviously returning a full function object to useland for every call would be considered wasteful, so the parser would need to call these as before. 2. Returning a native "Function" class, an __invokeable hybrid of Callable and Reflection; $method = MyClass::StaticFunction; $method(1, 2, 3); $method = $inst->my_function; /* bind to $inst */ $method(1, 2, 3); $method->getName(); $method->getArgumentCount(); $method->getBinding(); 3. Returning closures when the argument list includes one or more late-bound values, so we can finally put the pipe operator to bed at the same time as getting a bunch of other power from it. $method = MyClass::StaticFunction($1, 'Arg 1', 'Arg 3); $method('Arg 1'); $method = $inst->my_function('Arg 1', 'Arg 2', $1); $method('Arg 3'); chain( 'Random String', func_1($1, 'Hello', 'World'), func_2($1, 'Peace', 'Out'), func_3('ThisOneNeeds', 'Arg3ReplacingInstead', $1), func_3($1, $1, 'HowAboutOneWhichUsesTheSameArgumentTwice') ); function chain($start, ... $fns) { foreach ($fns as $fncall) { $start = $fncall($start); } return $start; } -- Mark Randall -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] Suggestion Method Constant
> > I also thought about the same for functions, just to be even more > consistent. > my_func::function I already had the exact same ideas, but didn't propose them yet. $obj::foo::method could be used for instance methods, while Obj::foo::method could be for static methods. Regards, Niklas
Re: [PHP-DEV] Suggestion Method Constant
I also thought about the same for functions, just to be even more consistent. my_func::function On 12 Oct 2017 23:32, "Sara Golemon"wrote: > On Thu, Oct 12, 2017 at 2:33 PM, Michael Döhler > wrote: > > I am open for any approach, but maybe we have to differentiate between > class constants and method references? > > > Given the discussion we had around the namespace separator (and why we > DIDN'T go with ::), there may be similar issues here. Maybe not, > given the final component is specifically T_METHOD, but it should be > prototyped to be sure. > > As to what such a reference would evaluate to: Foo::bar::method -> [ > Foo::class, 'bar' ] as Michael Döhler suggests seems the obvious > answer, but (Foo::class.'::bar') may be what some would expect. > Ideally we'd have first-class references to functions. > > -Sara >
Re: [PHP-DEV] Suggestion Method Constant
On Thu, Oct 12, 2017 at 2:33 PM, Michael Döhlerwrote: > I am open for any approach, but maybe we have to differentiate between class > constants and method references? > Given the discussion we had around the namespace separator (and why we DIDN'T go with ::), there may be similar issues here. Maybe not, given the final component is specifically T_METHOD, but it should be prototyped to be sure. As to what such a reference would evaluate to: Foo::bar::method -> [ Foo::class, 'bar' ] as Michael Döhler suggests seems the obvious answer, but (Foo::class.'::bar') may be what some would expect. Ideally we'd have first-class references to functions. -Sara -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] Suggestion Method Constant
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: > > 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 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 : >> > >> > 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, >
Re: [PHP-DEV] Suggestion Method Constant
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: > > 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, -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] Suggestion Method Constant
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öhlerwrote: > 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 : > > > > 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, >
[PHP-DEV] Suggestion Method Constant
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,