Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:33579
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain chiaraquartet.net from 38.99.98.18 cause and error)
Message-ID: <4753B087.4020206@chiaraquartet.net>
Date: Mon, 03 Dec 2007 01:30:15 -0600
User-Agent: Thunderbird 2.0.0.6 (X11/20071022)
MIME-Version: 1.0
To: Stanislav Malyshev <stas@zend.com>
CC: internals Mailing List <internals@lists.php.net>
References: <4731278C.8020301@chiaraquartet.net> <4731F977.4080502@zend.com>
In-Reply-To: <4731F977.4080502@zend.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] ignored patches
From: greg@chiaraquartet.net (Gregory Beaver)

Stanislav Malyshev wrote:
> As for multiple namespaces per file, it adds certain complications, both
> syntax-wise and engine-wise, so I'm still not 100% convinced it is worth
> it.

Which are?

Remember, we both found, independently, that combining separate files
yields from a 10-30% performance increase.  I have only talked to 2
developers who would be using namespaces that don't want this feature.
Of course, these two developers are the only people who would be using
namespaces with commit access to the Zend/ tree, but that doesn't make
the feature unnecessary.  If you'd like, I could put you in contact with
developers who have been struggling with combining files for several
years now.

Anecdotally, I heard of a recent file-combining optimization to a very
popular CMS that resulted in a 45% performance improvement.  Improving
the SQL queries led to only 9% improvement, so really the only reason
not to implement the multiple namespaces per-file patch is if you
actually *want* a large number of php devs to be annoyed at you :)

Thanks,
Greg