Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:66694
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain pcservice.co.za designates 67.18.44.21 as permitted sender)
MIME-Version: 1.0
Reply-To: pierre@pcservice.co.za
In-Reply-To: <20.05.17382.B0318415@pb1.pair.com>
References: <CACv1KMh_ahrK=bqsESzBq50KmfQxmZht-NR6Dc8acykMt1e06w@mail.gmail.com>
 <CAJbumGNP=fAcQABrxa_1P1m0KcazEXp731PfSc0kHi23673xKQ@mail.gmail.com>
 <CA+_UWzpccY6NQkwHpnfw7P37nfK003zwACj6LA1gA+=YSj-PyA@mail.gmail.com>
 <CAJbumGNs-yUBktBvvDOGRTcgteX_JsqQmspd+GQSOAo8KgvrAQ@mail.gmail.com>
 <CAAEi=BO8qVJNe_Yi0=9vSn7MgDjPi=cCU8K2241O420OQM9X4A@mail.gmail.com> <20.05.17382.B0318415@pb1.pair.com>
Date: Tue, 19 Mar 2013 09:37:43 +0200
Message-ID: <CAJbumGM6x4icDPpDfmR3dz1C9wkwrBsj8ouOgP9=HrRKGkcWBw@mail.gmail.com>
To: Bruno CHALOPIN <bruno@chalopin.fr>
Cc: PHP Development <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=bcaec53f92252303a004d8423086
Subject: Re: [PHP-DEV] __invokeStatic() method
From: pierre@pcservice.co.za (Pierre du Plessis)

--bcaec53f92252303a004d8423086
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

> Hi,
>
> Le Mon, 18 Mar 2013 09:07:43 +0200, Mat=C4=ABss Roberts Treinis a =C3=A9c=
rit :
> > Not only that. This potentially might break compatibility with many
> > software products already out there.
>
> I don't see how it could break existing software as it is not a
> modification of an existing method but a brand new one.
>


It would break existing software if you have a class and function with the
same name.
Consider the following example:

class foo {
}

function foo()
{

}


Now what if you have several calls to foo() in your existing application?
With the new change, will those calls call the function, or invoke the
__invokeStatic method if it is available?



>
> > Also, this might lead to many
> > misunderstandings and, in fact, ambiguous code. Consider the sample.
> >
> > $name =3D 'something';
> > $something =3D $name(); // What is this - a function call or object?
> >
> > Fact is, we can not know that unless a) do a search in code b) var_dump=
?
>
> As long as you use syntax like $foo =3D new $bar() or $foo =3D $bar(), yo=
u'll
> always wonder if the function/class behind $bar exist or not, etc...
> And it is easy to remove any ambiguity by using $something =3D $functionN=
ame
> () or $something =3D $className() or add proper comments. It's only up to
> the dev.
>
> I find that __invokeStatic() could be a quite cool syntactic sugar.
>
> My 2 cents.
>
> Bruno


I'm not against the function, just the implementation of it. __invokeStatic
might be useful in some (rare) cases,
but I don't think the proposed syntax will work.
Also I'm sure that most use cases can anyway be solved by using the
__callStatic method

--bcaec53f92252303a004d8423086--