Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:41148 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 4745 invoked from network); 16 Oct 2008 17:12:02 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 16 Oct 2008 17:12:02 -0000 Authentication-Results: pb1.pair.com smtp.mail=greg@chiaraquartet.net; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=greg@chiaraquartet.net; sender-id=unknown Received-SPF: error (pb1.pair.com: domain chiaraquartet.net from 208.83.222.18 cause and error) X-PHP-List-Original-Sender: greg@chiaraquartet.net X-Host-Fingerprint: 208.83.222.18 unknown Linux 2.6 Received: from [208.83.222.18] ([208.83.222.18:37095] helo=mail.bluga.net) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 5B/95-12818-0E577F84 for ; Thu, 16 Oct 2008 13:12:01 -0400 Received: from mail.bluga.net (localhost.localdomain [127.0.0.1]) by mail.bluga.net (Postfix) with ESMTP id F380DC1069E; Thu, 16 Oct 2008 10:11:51 -0700 (MST) Received: from pcp077519pcs.unl.edu (pcp077519pcs.unl.edu [129.93.148.126]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.bluga.net (Postfix) with ESMTP id ACBE2C10691; Thu, 16 Oct 2008 10:11:51 -0700 (MST) Message-ID: <48F775DD.5010202@chiaraquartet.net> Date: Thu, 16 Oct 2008 12:11:57 -0500 User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070807) MIME-Version: 1.0 To: Stanislav Malyshev CC: Lukas Kahwe Smith , PHP Developers Mailing List References: <48F653FF.5010106@chiaraquartet.net> <48F75FA1.7020505@zend.com> <0C55B977-3835-4CB0-A23B-8AA684B71C18@pooteeweet.org> <48F772CD.80600@zend.com> In-Reply-To: <48F772CD.80600@zend.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP Subject: Re: [PHP-DEV] my last attempt at sanity with namespaces From: greg@chiaraquartet.net (Greg Beaver) Stanislav Malyshev wrote: > Namespaces aren't autoloadable, classes are. But what I see happening > is that people would start converting excisting code, and since they > are human they will inevitable forget or miss class here and there. > And it would work, and pass all tests, and look fine and dandy on the > outside - but under the water it would contain the performance bomb of > non-cacheable exhaustive autoload search. It is a big disservice for > our users to put them into this situation where you need to be an > expert to even notice where the problem is - especially that we > *already* know the problem exists and we *know* how to fix it. Why not > just fix it? Hi Stas, Was your proposal to do this for name resolution: