Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:66697
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.214.50 as permitted sender)
To: internals@lists.php.net
Cc: Bruno CHALOPIN <bruno@chalopin.fr>
Date: Tue, 19 Mar 2013 09:13:08 +0100
Message-ID: <1683535.aSTGThNVFk@rofl>
User-Agent: KMail/4.10.1 (Linux/3.8.3-k10-bof; KDE/4.10.1; x86_64; ; )
In-Reply-To: <4F.50.28284.AA918415@pb1.pair.com>
References: <CACv1KMh_ahrK=bqsESzBq50KmfQxmZht-NR6Dc8acykMt1e06w@mail.gmail.com> <CAJbumGM6x4icDPpDfmR3dz1C9wkwrBsj8ouOgP9=HrRKGkcWBw@mail.gmail.com> <4F.50.28284.AA918415@pb1.pair.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
Subject: Re: [PHP-DEV] __invokeStatic() method
From: php@bof.de (Patrick Schaaf)

On Tuesday 19 March 2013 02:54:19 Bruno CHALOPIN wrote:

> Now I don't see why in the world a class and a function could share the same 
name.

Well, for one, I might have code like this:

class Foo {
	public static the_usual() {
		static $instance;
		if (!isset($instance)) $instance = new Foo();
		return $instance;
	}
}

function Foo() {
	Foo::the_usual();
}

.....

> Regarding conventions, a class name should begin with an uppercase character 
and a function a lowercase one.

That' s a convention. That means that noone has to adhere to it. I don't.

> I don't see any relevant use case where a class
> and a function should share the same name.

Don't let yourself be limited by your imagination.

best regards
  Patrick