Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:18699 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 36705 invoked by uid 1010); 7 Sep 2005 21:19:47 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 36690 invoked from network); 7 Sep 2005 21:19:47 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 7 Sep 2005 21:19:47 -0000 X-Host-Fingerprint: 67.18.30.226 unknown Windows 2000 SP4, XP SP1 Received: from ([67.18.30.226:4099] helo=aspteam01.asp-team.com) by pb1.pair.com (ecelerity 2.0 beta r(6323M)) with SMTP id 20/D0-23233-3795F134 for ; Wed, 07 Sep 2005 17:19:47 -0400 Received: from [127.0.0.1] ([24.97.207.99]) by asp-team.com with MailEnable ESMTP; Wed, 07 Sep 2005 16:19:39 -0500 Message-ID: <431F596F.9050604@unFocus.com> Date: Wed, 07 Sep 2005 17:19:43 -0400 User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317) X-Accept-Language: en-us, en MIME-Version: 1.0 To: internals@lists.php.net Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Antivirus: avast! (VPS 0536-2, 09/07/2005), Outbound message X-Antivirus-Status: Clean Subject: Namespaces Question From: CaptainN@unFocus.com (Kevin Newman) Hello, I'm new here, but I have some ideas that I would like to share about implementing namespaces, but I'd like to know what the current state and issues of namespaces are before I share them. I've read that there is a possible performance consideration involving two hash table lookups when using the scoping operator (str::replace etc.). I've also read that there were some language design issues to consider. What are the other issues? I have done quite a bit of searching on google, zend.com and other places to try to find the answer to why namespaces were removed from php 5, but was unable to find anything concrete. Some kind of a summary would be most appreciated. :-) Thank you, Kevin N.