Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:23615
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Message-ID: <4471C87A.3030904@pooteeweet.org>
Date: Mon, 22 May 2006 16:19:38 +0200
User-Agent: Thunderbird 1.5.0.2 (Windows/20060308)
MIME-Version: 1.0
To: PHP Developers Mailing List <internals@lists.php.net>,
	flconseil@yahoo.fr
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [Fwd: PHP Release Management Wiki PHPTODO:PhP60]
From: smith@pooteeweet.org (Lukas Kahwe Smith)

Hi,

replying to internals ..
this was originally a comment made on the following site:
http://oss.backendmedia.com/PhP60

 > flconseil@yahoo.fr writes:
 >
 > What about improving the autoload mechanism ?
 > Suggestions :
 >
 > - When autoload() is called, it is impossible to know if a class or
 > an interface is required. In my resolution system, I must search both.
 > - Should be able to autoload functions (at least) and constants. But
 > global variables must be kept outside.
 > - Most important: The autoload mechanism should provide a layered
 > callback registration. As long as it is implemented a an unique

these sounds like interesting feature requests ...

 > autoload() function, it is impossible to use it in a library package. 
 > Multiple autoload callbacks should be allowed to be registered at the
 > same time.

this is already support by SPL:
http://php.net/~helly/php/ext/spl/group__SPL.html#gaf60ea8bbef114980007c6067850c150

regards,
Lukas