Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:40216
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain zend.com designates 212.25.124.163 as permitted sender)
Message-ID: <48BD7186.2040009@zend.com>
Date: Tue, 02 Sep 2008 10:01:58 -0700
Organization: Zend Technologies
User-Agent: Thunderbird 2.0.0.16 (Windows/20080708)
MIME-Version: 1.0
To: Marcus Boerger <helly@php.net>
CC: Gregory Beaver <greg@chiaraquartet.net>, 
 Lukas Kahwe Smith <mls@pooteeweet.org>,
 PHP Internals List <internals@lists.php.net>
References: <0E6B0C09-99C4-4843-A8E6-0B015EB98B4E@pooteeweet.org> <48BAF947.6060708@chiaraquartet.net> <48BCF08A.7080108@zend.com> <1616152782.20080902135428@marcus-boerger.de>
In-Reply-To: <1616152782.20080902135428@marcus-boerger.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Re: namespace RFC
From: stas@zend.com (Stanislav Malyshev)

Hi!

> My guess is that it allows for development with heavy __autload usage and
> then doing deployment based on static analysis where each target page
> results in one large php file generated from that analysis. So there won't
> be any overhead and each script target would be a single target of its own.

So each target (like each page, MVC action, etc.) would have its own 
huge PHP file that has all classes used there? I guess for some 
applications that could work, for others, more dynamic, that would fail 
miserably. The maintainability of such thing is also challenging.
It would be nice to have some real-life examples of how such things work 
out - so far I have seen only theory and synthetic benchmarks, which are 
interesting, but not necessary what would happen on real project.
-- 
Stanislav Malyshev, Zend Software Architect
stas@zend.com   http://www.zend.com/
(408)253-8829   MSN: stas@zend.com