Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:66696
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain pcservice.co.za designates 67.18.68.4 as permitted sender)
MIME-Version: 1.0
Reply-To: pierre@pcservice.co.za
In-Reply-To: <4F.50.28284.AA918415@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> <CAJbumGM6x4icDPpDfmR3dz1C9wkwrBsj8ouOgP9=HrRKGkcWBw@mail.gmail.com>
 <4F.50.28284.AA918415@pb1.pair.com>
Date: Tue, 19 Mar 2013 10:08:51 +0200
Message-ID: <CAJbumGMfU5mj9ngPSSYNQC0sgMb5W8dOmJ40SygWz8YxCFSxRQ@mail.gmail.com>
To: Bruno CHALOPIN <bruno@chalopin.fr>
Cc: PHP Development <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=20cf3074b16a751cc904d8429fd6
Subject: Re: [PHP-DEV] __invokeStatic() method
From: pierre@pcservice.co.za (Pierre du Plessis)

--20cf3074b16a751cc904d8429fd6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

> Le Tue, 19 Mar 2013 09:37:43 +0200, Pierre du Plessis a =E9crit :
> > 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, o=
r
> > invoke the __invokeStatic method if it is available?
>
> It will clearly technically lead to a problem. Now I don't see why in the
> world a class and a function could share the same name. Regarding
> conventions, a class name should begin with an uppercase character and a
> function a lowercase one. I don't see any relevant use case where a class
> and a function should share the same name.
>
>
PHP doesn't care about uppercase or lowercase when it comes to function
names.
Have a look at http://3v4l.org/cePT5 for an example.
And not everybody uses conventions anyway (although they should)

Although it is not common to have a class and function have the same name,
it can happen.
Take the following code as an example.

class Debug {
    public static dump($var)
    {
        // some code to debug $var
    }
}

function debug($var)
{
    return Debug::dump($var);
}

The problem is clear if you have a __invokeStatic method in the debug
class, and you want to make a call to debug().

--20cf3074b16a751cc904d8429fd6--