Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:39939 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 5666 invoked from network); 13 Aug 2008 22:43:31 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 13 Aug 2008 22:43:31 -0000 Authentication-Results: pb1.pair.com header.from=greg@chiaraquartet.net; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=greg@chiaraquartet.net; spf=permerror; 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:60816] helo=mail.bluga.net) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id D2/10-05165-19363A84 for ; Wed, 13 Aug 2008 18:43:30 -0400 Received: from mail.bluga.net (localhost.localdomain [127.0.0.1]) by mail.bluga.net (Postfix) with ESMTP id 21C8BC0DCEF; Wed, 13 Aug 2008 15:43:16 -0700 (MST) Received: from [192.168.0.106] (CPE-76-84-4-101.neb.res.rr.com [76.84.4.101]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.bluga.net (Postfix) with ESMTP id 39480C0DCE8; Wed, 13 Aug 2008 15:43:15 -0700 (MST) Message-ID: <48A36394.2040408@chiaraquartet.net> Date: Wed, 13 Aug 2008 17:43:32 -0500 User-Agent: Thunderbird 2.0.0.16 (X11/20080724) MIME-Version: 1.0 To: Lukas Kahwe Smith CC: Stanislav Malyshev , Marcus Boerger , internals@lists.php.net References: <909776579.20080803142659@marcus-boerger.de> <840985F2-A701-4BE4-91F6-F6B39048CF9B@pooteeweet.org> <48A09FF4.1030101@zend.com> <7f3ed2c30808111411t51553771j389f05c3436bc625@mail.gmail.com> <48A0C415.9090104@zend.com> <48A0D579.2000000@zend.com> <48A0DBAE.2010401@zend.com> <496879481.20080812153636@marcus-boerger.de> <279600845.20080812225135@marcus-boerger.de> <1218621323.4926.1.camel@localhost> <1341995942.20080813152134@marcus-boerger.de> <1218634532.4926.5.camel@localhost> <1714092517.20080813194342@marcus-boerger.de> <48A32817.4020105@zend.com> <10910129111.20080813213721@marcus-boerger.de> <48A33D86.1010806@zend.com> <59637275.20080813221213@marcus-boerger.de> <48A34180.8070601@zend.com> <0D64C8C4-2136-4D6B-9EBD-B5956C3044FC@pooteeweet.org> In-Reply-To: <0D64C8C4-2136-4D6B-9EBD-B5956C3044FC@pooteeweet.org> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP Subject: Re: [PHP-DEV] Inconsistencies in 5.3 From: greg@chiaraquartet.net (Gregory Beaver) Lukas Kahwe Smith wrote: > > On 13.08.2008, at 22:18, Stanislav Malyshev wrote: > >> Simply include a script from two locations with different namespaces >> or one >>> >>> with namespace and the otherone without. >> >> I'm afraid you misunderstand how namespaces work. As I explained >> numerous times, namespaces are file-local, and this when including >> file, it does not matter a bit what was including context. > > I think Marcus is talking about files that are included that do not > specify a namespace explicitly. In this situation the context does matter. > > We do not know if the developer in question is aware that the context > would matter in this case. Actually like I said in a previous email it > would be nice to at least not throw a warning if the file that is > included specifies an explicit namespace (I assume that is possible?). > Maybe adding a new "include" is a solution. This way developers can say > explicitly what they want to do without having to suppress the warning. > Then again quickly some smartass developer is going to teach people that > these annoying warnings go away if you just use this new include > everywhere. Then again, I am not sure if I even have my head wrapped > around this entire namespace thing. Hi, Currently, if you include a file within a class method that contains function definitions, they remain functions outside the class. If you include a file that contains a class. In short, only global cpde is executed in the scope, and there is no precedent in PHP to redefine re-usable elements based on scope. Why would namespaces be any different? This whole argument makes no sense to me. Greg