Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:108531
Date: Thu, 13 Feb 2020 07:57:56 +0000
User-Agent: K-9 Mail for Android
In-Reply-To: <CAD5P3=Jkr6pbO7LSc3uskFrAHEa1JYsEvDyaQm8OPbAnWfK=xQ@mail.gmail.com>
References: <CAD5P3=JwFK03L-DWJYaa0dbBj1chbef_=K-vyawLNeoAz7dHjA@mail.gmail.com> <CALSrLtYm+TSEwo+05JC6LXrQsfzb32pQ24Y7gDUmm-7+NwYi8w@mail.gmail.com> <CAOWwgpm43=hoCvsskq2qyhB3yVxntLAYC8hQjQwd9dnvQ=GKkg@mail.gmail.com> <CAD5P3=L8bQ4bp5i5f=SdOP-=Wmn6TSj6+4Jzw76WRwJ=89evtw@mail.gmail.com> <CAF+90c-myY2NeKcaTRH3zDcwxRC95RhKnm1MPTGN68WUq4RPAA@mail.gmail.com> <CAPKYkKy-NwDmpN_5Zet8Oz9JLVzu11PmODP6byBYuJry3TUvbg@mail.gmail.com> <CAD5P3=K5UHUyfJD4prjhyEuUqkNuuHcLzq_DiLMX-KE644eo5w@mail.gmail.com> <9829e5c9-9e32-9686-8ff2-ec7930dda709@gmail.com> <CAD5P3=LbrotNxH1Rb-f7A8sdHy5pfa+0E3j_tXLdmcx6SnrbXg@mail.gmail.com> <20d9da97-243a-a171-0412-7298b79e4dde@gmail.com> <CAD5P3=Jkr6pbO7LSc3uskFrAHEa1JYsEvDyaQm8OPbAnWfK=xQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain;
 charset=utf-8
Content-Transfer-Encoding: quoted-printable
CC: PHP Internals List <internals@lists.php.net>
Message-ID: <A382F5D9-EF38-4858-AC59-556FBA65F950@gmail.com>
Subject: Re: [PHP-DEV] [RFC]
From: rowan.collins@gmail.com (Rowan Tommins)

On 12 February 2020 23:12:34 GMT+00:00, Manuel Canga <manuelcanga@gmail=2Ec=
om> wrote:
>El mi=C3=A9=2E, 12 feb=2E 2020 23:01, Rowan Tommins <rowan=2Ecollins@gmai=
l=2Ecom>
>escribi=C3=B3:
>In your example, you has the same options:
>
>>
>1=2E Change import
>2=2E Add namespace:
>
>['Acme\Global\I18N',\translate::function]


There is no collision between 'Foo::translate()' and 'translate()', so the=
re is no reason to change the import=2E That's true of executing the functi=
ons, so it should remain be true of resolving them to strings=2E



>Explain:
>
>When you do: [ class, method ] or [ $object, method ]=2E Method has not
>namespace, you write it without namespace( like global functions )


I think this is where we are thinking differently=2E A method name is not =
"like a global function", it's just a name; it doesn't belong in the same c=
ategory=2E=20

You might have any number of classes that use the same method name, but wi=
th completely different parameters and purpose, so "a method named foo" isn=
't a useful concept outside some specific class or interface=2E

On the other hand, you can only have one function with a particular fully-=
qualified name, and the proposed feature is a way of referencing that=2E



>Other example:
>
>$class =3D \MyClass::class;
>$method =3D \method::function;
>
>and=2E=2E=2E
>
>$class =3D '\MyClass';
>$method =3D 'method';
>
>$obj =3D new $class();
>$obj->$method();
>
>Both are the same, but first is more semantic=2E


This isn't semantic at all - it works only because \method::function happe=
ns to return the string you want, but so does \method::class; neither is ac=
tually labelling it as what it is, which is a method within class \MyClass=
=2E

Importantly, it might not work at all, if ::function gives an error if the=
 function doesn't exist=2E=20

Regards,

--=20
Rowan Tommins
[IMSoP]