Re: Inconsistencies in 5.3
| From: | Greg Beaver | Date: | Mon, 04 Aug 2008 20:45:00 +0000 |
| Subject: | Re: Inconsistencies in 5.3 | ||
| References: | 1 2 3 4 5 6 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-39643@lists.php.net to get a copy of this message | ||
Hannes Magnusson wrote:
On Mon, Aug 4, 2008 at 10:32, Lukas Kahwe Smith <mls@pooteeweet.org> wrote:I said it before, and I'll say it again, I am fine with this approach, especially with Dmitry's (old) proposed syntax allowing namespace-less code within namespace {}: <?php namespace foo { class blah{} } namespace { // put legacy code here $a = new blah; } ?> GregOn 04.08.2008, at 10:28, Stefan Priebsch wrote:Fair enough. Then lets keep the name "namespace" and use curly braces.Hannes Magnusson schrieb: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).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.