Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:33933 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 79696 invoked by uid 1010); 11 Dec 2007 21:41:42 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 79681 invoked from network); 11 Dec 2007 21:41:42 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 11 Dec 2007 21:41:42 -0000 Authentication-Results: pb1.pair.com smtp.mail=jochem@iamjochem.com; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=jochem@iamjochem.com; sender-id=unknown Received-SPF: error (pb1.pair.com: domain iamjochem.com from 194.109.193.121 cause and error) X-PHP-List-Original-Sender: jochem@iamjochem.com X-Host-Fingerprint: 194.109.193.121 mx1.moulin.nl Linux 2.6 Received: from [194.109.193.121] ([194.109.193.121:47863] helo=mx1.moulin.nl) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 2B/1E-17330-5140F574 for ; Tue, 11 Dec 2007 16:41:42 -0500 Received: from localhost (localhost [127.0.0.1]) by mx1.moulin.nl (Postfix) with ESMTP id 3C35024C7C2; Tue, 11 Dec 2007 22:41:38 +0100 (CET) X-Virus-Scanned: amavisd-new at moulin.nl Received: from mx1.moulin.nl ([127.0.0.1]) by localhost (mx1.moulin.nl [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id frD2b7nB6f48; Tue, 11 Dec 2007 22:41:33 +0100 (CET) Received: from [10.0.13.54] (ip129-15-211-87.adsl2.versatel.nl [87.211.15.129]) by mx1.moulin.nl (Postfix) with ESMTP id E292B24C617; Tue, 11 Dec 2007 22:41:32 +0100 (CET) Message-ID: <475F0410.5010704@iamjochem.com> Date: Tue, 11 Dec 2007 22:41:36 +0100 User-Agent: Thunderbird 2.0.0.9 (Windows/20071031) MIME-Version: 1.0 To: Stanislav Malyshev CC: =?ISO-8859-1?Q?David_Z=FClke?= , internals@lists.php.net References: <11970653983080000@9866357972520000.9866341568840000> <475BDDF1.7040605@ctindustries.net> <1723341090.20071210220025@marcus-boerger.de> <1197323296.3922.5.camel@sbarrow-desktop> <00A2E2156BEE8446A81C8881AE117F199A0715@companyweb> <475ED038.3080004@zend.com> <7F9E1E02-FF89-474B-9E94-007747B3637A@bitxtender.com> <475EF175.2030304@zend.com> <475F01B1.8090407@zend.com> In-Reply-To: <475F01B1.8090407@zend.com> X-Enigmail-Version: 0.95.5 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: AW: [PHP-DEV] Namespace resolution From: jochem@iamjochem.com (Jochem Maas) Stanislav Malyshev wrote: >> You would now have to go through all ten autoloaders before you can >> decide that no userspace class DateTime exists in any namespace, and >> thus the PHP internal class DateTime may be used. > > Even one autoloader is bad enough to not even have to consider the case > of ten autoloaders. Remember, autoloader is filesystem access. > Filesystem access on each class mention is a disaster. it's just slow. regardless namespaces need to work in conjunction with autoload in a perdictable and understandable manner ... I get the distinct impression that namespaces+autoload is going to introduce a serious wtf factor. given that autoload is 'out there' and the raison d'etre of namespaces is, amongst other things, to enable better leveraging of third party code namespaces must concede to autoload if only for the reason that one is garanteed to have to deal with both together at some point if one is ever to seriously make use of third party namespaced code. as an aside, is autoload becoming the new 'magic_quotes'? > >> like a fool when you're tired of coming up with arguments. You very >> well know I meant "import". Reply to the suggestion in a respectful >> manner, or give it a miss. > > I'm afraid I still do not understand what did you mean. Could you > explain in more detail?