Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:41437
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain fmethod.com from 69.16.228.148 cause and error)
Message-ID: <69907CB6763C4164A1AE82D659B80286@pc>
To: <internals@lists.php.net>
Date: Mon, 27 Oct 2008 13:36:55 +0200
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0095_01C93839.13AE4850"
Subject: Clarifying the resolution rules
From: sv_forums@fmethod.com ("Stan Vassilev | FM")

------=_NextPart_000_0095_01C93839.13AE4850
Content-Type: text/plain;
	charset="windows-1251"
Content-Transfer-Encoding: quoted-printable

Hi,


Now that we have a separator, it's time to clarify what happened to the =
resolution order for functions and classes, which if I read Greg's =
messages, is still not clearly defined.

1) I think we've established that autoloading + fallback for classes is =
unworkable, as it either causes excessive autoload triggering, or =
alternatively allows internal classes to override unloaded but =
to-be-autoloaded namespaced classes. Then why is it still under =
consideration?

2) Making the backslash optional for internal functions means popular =
drop-in replacements for internal functions and extensions in global =
space, which work today, will break in a namespace, examples: =
libcurlemu. Also check any comments on PECL functions on php.net, and =
you'll see a myriad of drop-in replacements people use today.

Also, for those who want to automatically convert their internal =
functions to backslash prefix for use in namespaces, you can use this =
quick snippet I wrote (works in 5.2.x too):

http://pastebin.com/f13125acd

I don't make guarantees it's perfect, but it can be improved and given =
to people as a porting aid.

Opinions about how disruptive a mandatory backslash for global symbols =
*in namespaces* would be, are welcome. Keep in mind that making the =
backslash optional will lead to code breakage (such as for above drop-in =
replacements, class autoloading etc.) and slower performance (runtime =
resolution of function calls).

Think of it as file paths. When you're inside a directory you need to =
prefix your path with "/" (eg "\") to refer to the root, but you don't =
need to do that when you're in the root directory.

Regards,
Stan Vassilev 
------=_NextPart_000_0095_01C93839.13AE4850--