Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:39650
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain at.wakwak.com designates 219.103.130.24 as permitted sender)
Message-ID: <4897E6D3.7080403@at.wakwak.com>
Date: Tue, 05 Aug 2008 14:36:19 +0900
User-Agent: Thunderbird 2.0.0.16 (Windows/20080708)
MIME-Version: 1.0
To: Marcus Boerger <helly@php.net>
Cc: Lukas Kahwe Smith <mls@pooteeweet.org>,
        Stefan Priebsch <stefan.priebsch@e-novative.de>,
        Hannes Magnusson <hannes.magnusson@gmail.com>,
        Dmitry Stogov <dmitry@zend.com>, internals@lists.php.net
References: <909776579.20080803142659@marcus-boerger.de> <4896A7C4.8090503@zend.com> <7f3ed2c30808040055r377369d0l86f7c39cea7d94b2@mail.gmail.com> <4896BDB3.7000003@e-novative.de> <99710BD7-2224-4AA2-B2DD-1B6A4A5C0DA8@pooteeweet.org> <4110342533.20080804104113@marcus-boerger.de> <71D8CF46-882A-4120-A4D7-B62646703120@pooteeweet.org> <147844133.20080804105816@marcus-boerger.de>
In-Reply-To: <147844133.20080804105816@marcus-boerger.de>
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Inconsistencies in 5.3
From: moriyoshi@at.wakwak.com (Moriyoshi Koizumi)

Marcus Boerger wrote:
> Hello Lukas,
> 
> Monday, August 4, 2008, 10:49:43 AM, you wrote:
> 
> 
>> On 04.08.2008, at 10:41, Marcus Boerger wrote:
> 
>>> Hello Lukas,
>>>
>>> Monday, August 4, 2008, 10:32:26 AM, you wrote:
>>>
>>>
>>>> On 04.08.2008, at 10:28, Stefan Priebsch wrote:
>>>>> Hannes Magnusson schrieb:
>>>>>> I don't think anyone but him likes multiple namespaces per file.  
>>>>>> I do
>>>>>> remember a PhD thesis sized mail from him explaining why multiple
>>>>>> namespaces per file was needed though (can hardly believe anyone  
>>>>>> read
>>>>>> the whole thing..).
>>>>> In some deployment processes, multiple PHP files are merged together
>>>>> into one file. Symfony, for example, does this, at least optionally.
>>>
>>>> Right, this is common practice to reduce disk I/O without having to
>>>> make development too hard. Also that way people can pick and choose
>>>> what they want to include (like not all drivers of a DBAL).
>>> If an edgecase optimization is th eonly reason then I am against this
>>> even more.
> 
> 
>> its not an edge optimization .. like i said its "common practice" in  
>> many PHP frameworks. this way they can more easily develop the code,  
>> while not having to suffer the drawbacks from a lot of disk I/O from  
>> files that need to be loaded in every request anyways.
> 
>> and those frameworks are the main users of namespaces, because they  
>> pull in libs from all sorts of libraries, add plugins etc.
> 
> In that case lets have curly braces at least to be consistent with the rest
> of the language as every other grouping statement has curly braces.

I think the point is that PHP doesn't have the concept of compilation 
units unlike major namespaced programming languages such as C++ and 
Java. PHP so far chose to differentiate grammatical contexts with braces 
or blocked statements, so should namespace.

Moriyoshi
-- 
Moriyoshi Koizumi <moriyoshi@at.wakwak.com>