Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:100898
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain me.com designates 17.36.66.14 as permitted sender)
Content-type: text/plain; charset=us-ascii
MIME-version: 1.0 (1.0)
In-reply-to: <E3.18.07885.D0261E95@pb1.pair.com>
Date: Sat, 14 Oct 2017 12:41:35 +0200
Cc: internals@lists.php.net
Content-transfer-encoding: quoted-printable
Message-ID: <A8C8B794-8854-42A5-8A81-CF0EFBB74AD1@me.com>
References:
 <CA+aNemZ-_L-fMdWMFf2jEo55sKWEM8C_87_hQh=LbjHBhw7Kww@mail.gmail.com>
 <E3.18.07885.D0261E95@pb1.pair.com>
To: Andrea Faulds <ajf@ajf.me>
Subject: Re: [PHP-DEV] Re: Suggestion Method Constant
From: michaeldoehler@me.com (=?utf-8?Q?Michael_D=C3=B6hler?=)

Hi,

maybe the introduce of a complete new syntax for method references would sol=
ve the issues? Maybe coming back to e.g. "#" ("@" is still used for supressi=
ng errors,...)?

As mentions before all kinds can be simplified or? See:

MyClass#myMethod

#function

This should resolve in an object as mentioned before, in this object you hav=
e further informations, e.g.

$ref =3D MyClass#myMethod;
$ref->isStatic();
...

I think an seperate solution for method/Funktion references is more realisti=
c than changing core things...

Greetings
Michael=20

> Am 14.10.2017 um 03:02 schrieb Andrea Faulds <ajf@ajf.me>:
>=20
> Hi Mathias,
>=20
> Mathias Grimm wrote:
>> I would like to suggest a method constant that could be used the same way=

>> we use the ::class one
>>=20
>> I don't have a strong personal preference but it could be something like:=

>>=20
>> MyController::myActionMethod::method, no sure about the internals but it
>> would be consistent with the one for the class.
>>=20
>> Cheers,
>=20
> I've long wanted to make constant lookups fall back to a closure of the co=
rrespondingly-named function, where one exists. so `strlen` would resolve to=
 a closure of strlen().
>=20
> Thing is that classes are weird. We sort of have three different things wi=
th sometimes-similar syntax: constants, methods and properties. foo::bar is a=
 constant, foo::bar() is a function, $foo->bar() is a function, but $foo->ba=
r is not a constant. So, if I want $foo->bar to resolve to a method, then $f=
oo::$bar should too, even though that makes no sense. The PHP static propert=
y syntax is the bane of my existence.
>=20
> --=20
> Andrea Faulds
> https://ajf.me/
>=20
> --=20
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>=20