Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:62886 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 3976 invoked from network); 7 Sep 2012 00:55:26 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 7 Sep 2012 00:55:26 -0000 Authentication-Results: pb1.pair.com header.from=smalyshev@sugarcrm.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=smalyshev@sugarcrm.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain sugarcrm.com designates 67.192.241.163 as permitted sender) X-PHP-List-Original-Sender: smalyshev@sugarcrm.com X-Host-Fingerprint: 67.192.241.163 smtp163.dfw.emailsrvr.com Linux 2.6 Received: from [67.192.241.163] ([67.192.241.163:48949] helo=smtp163.dfw.emailsrvr.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id E0/12-03079-DF549405 for ; Thu, 06 Sep 2012 20:55:26 -0400 Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp26.relay.dfw1a.emailsrvr.com (SMTP Server) with ESMTP id 09A3980182; Thu, 6 Sep 2012 20:55:23 -0400 (EDT) X-Virus-Scanned: OK Received: by smtp26.relay.dfw1a.emailsrvr.com (Authenticated sender: smalyshev-AT-sugarcrm.com) with ESMTPSA id 2EADF80130; Thu, 6 Sep 2012 20:55:21 -0400 (EDT) Message-ID: <504945F8.2070207@sugarcrm.com> Date: Thu, 06 Sep 2012 17:55:20 -0700 Organization: SugarCRM User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:15.0) Gecko/20120824 Thunderbird/15.0 MIME-Version: 1.0 To: Yahav Gindi Bar CC: "internals@lists.php.net" References: <504942C9.6050106@sugarcrm.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] Why are the PHP namespaces different compared to C++? From: smalyshev@sugarcrm.com (Stas Malyshev) Hi! > That's true, but we do got the ability to import only one class from > given namespace and classes aliasing so we can, for example, do > something like: When you import one name, you see this name in import statement. It's explicit. Global imports are not. I really hate to rehash discussion from years ago all from the start. Please believe we did think about it - including having special options, functions, configurations, INI entries, etc. for defining imports. It's not worth it to save couple of keystrokes on namespace prefix, really. Not everything should live in global space, that's the whole point of namespaces. -- Stanislav Malyshev, Software Architect SugarCRM: http://www.sugarcrm.com/ (408)454-6900 ext. 227