Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:17418 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 86260 invoked by uid 1010); 26 Jul 2005 21:54:07 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 86245 invoked from network); 26 Jul 2005 21:54:07 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 26 Jul 2005 21:54:07 -0000 X-Host-Fingerprint: 82.165.42.187 xhantos.de NetCache 5.3-5.5 Received: from ([82.165.42.187:59155] helo=xhantos.de) by pb1.pair.com (ecelerity 2.0 beta r(6227M)) with SMTP id 72/36-58254-EF0B6E24 for ; Tue, 26 Jul 2005 17:54:06 -0400 Received: from boost.home.ahk (p54A33CB0.dip0.t-ipconnect.de [84.163.60.176]) by xhantos.de (Postfix) with ESMTP id B70E89B427; Tue, 26 Jul 2005 23:54:17 +0200 (CEST) To: Marcus Boerger Cc: Jessie Hernandez , internals@lists.php.net In-Reply-To: <1374121835.20050726101045@marcus-boerger.de> References: <52.31.61486.E8DCDD24@pb1.pair.com> <1122328113.647.16.camel@boost.home.ahk> <538910800.20050725235918@marcus-boerger.de> <79.5B.58254.6DCA5E24@pb1.pair.com> <1374121835.20050726101045@marcus-boerger.de> Content-Type: text/plain Date: Tue, 26 Jul 2005 23:54:02 +0200 Message-ID: <1122414842.4938.13.camel@boost.home.ahk> Mime-Version: 1.0 X-Mailer: Evolution 2.2.3 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] [PATCH] Namespace Patch, Alpha 3 From: alex@kiesel.name (Alex Kiesel) On Tue, 2005-07-26 at 10:10 +0200, Marcus Boerger wrote: > > I still think the namespace import behavior should be separate from the > > __autoload function. Of course, this is just me. What does everyone else > > think? I'd like to gather opinions on which is preferred. I will also like > > to know if a separate class_path is preferred (as I have in my last patch) > > or if just leaving include_path is what most prefer. > > None of the above makes any sense. Look __autoload() is just bein called at > any place where a class is missing. So looking for the file first and then > loading __autoload(I) makes no sense whatsoever. IMO what we need here is a > default implementation for import behavior accomplished by __autoload(). So > for example "import ns:cls;" leads to "__autoload('ns:cls')". Here the SPL > default implementation would relpace all ':' with the directory divider '/' > or '\', append '.inc' or '.php' or '.inc.php' and append the result to all > directories in the include_path to look for the file. If were are to support > import with '*' the the autoload implementation would need to take care of > this and load all matching files. A user land implementation can easily > achieve that by using SPLs (Recursive)DirectoryIterator and FilterIterator. What are the options when having a PHP without SPL, then? That __autoload invocation chain once in discussion hasn't yet been implemented, right? Regards, -Alex