Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:26479
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 64.233.184.235 as permitted sender)
DomainKey-Status: good
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:in-reply-to:references:mime-version:content-type:message-id:cc:content-transfer-encoding:from:subject:date:to:x-mailer:sender;
        b=WB/wq7zYd0tNkgqKR/+mMVc/g0dSj64Ef17UddWCV3n86+hWKulSWo4m8sWAAqQNyANKl8TD//QD4cCZtffDPsRcn2NzZN9FwGaMqNkAIrd/UKMv/L38Ap8Gw+6zKAuNPKrA8itTiEXv9wvPWYwH9636euG3LqPvQfI9xxHVXQY=
In-Reply-To: <ej2ecr$p00$1@sea.gmane.org>
References: <4554AE0D.4080600@caedmon.net> <D268FFAD-6916-4EDE-9511-31F5BC774318@prohost.org> <ej2ecr$p00$1@sea.gmane.org>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-ID: <C5943228-21EB-4265-8DC3-3A573E1A05EA@prohost.org>
Cc: internals@lists.php.net
Content-Transfer-Encoding: 7bit
Date: Fri, 10 Nov 2006 13:13:52 -0500
To: Sebastian Bergmann <sb@sebastian-bergmann.de>
Sender: Ilia Alshanetsky <iliaal@gmail.com>
Subject: Re: [PHP-DEV] Namespaces in PHP 6 - ++$take
From: ilia@prohost.org (Ilia Alshanetsky)


On 10-Nov-06, at 12:54 PM, Sebastian Bergmann wrote:

> Ilia Alshanetsky wrote:
>> If anything it'll make code complex and intertwined, introduce  
>> serious
>> scope issue most people have not had to consider up until now and so
>> on. It will without a doubt increase language complexity as well,  
>> which
>> generally translates to a loss in performance.
>
>  Am I right to assume that both scoping and performance issues only  
> come
>  up if we were to implement an import() mechanism? If so, do we really
>  need import?
>
>  If not, then
>
>    namespace foo
>    {
>      class bar
>      {
>      }
>    }
>
>  would be "mangled" at compile-time into foo\bar and should not impose
>  any performance penalty or scoping issues.

As your key size increases the slower the key hash generation process  
becomes, if you look at the PHP's hash key generation code you'll see  
that it works best for 8 or less chars, anything longer and the  
performance starts to drop. Add to this case-sensitivity issues and  
you have an additional draw on your speed.

Obviously, by doing things at compile time you reduce overhead, so it  
is a good idea, but it will not eliminate the performance penalties,  
it'll probable halve them however.

Ilia Alshanetsky