Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:33667
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 64.233.162.232 as permitted sender)
DomainKey-Status: bad
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references;
        b=Ikr8U7MySIsQEm0xRbLWM/lqgoSOZlM4OBI93YLK0Vlz+KPLCxKmlos4xdpUBb8rmy7/Y1m+rch71AkD9uwpGCjyXDSQUiNijPefW+IK431x6Ay0IdIOxSzQk6AZFosdumUh5InnDBt9RJO10su48L1CVe6sCnM37LmrY8SpSuQ=
Message-ID: <52dbac0f0712041013p1fb023cag4f2ba8a2a067a099@mail.gmail.com>
Date: Tue, 4 Dec 2007 15:13:01 -0300
To: "Gregory Beaver" <greg@chiaraquartet.net>
Cc: "internals Mailing List" <internals@lists.php.net>
In-Reply-To: <47558C21.7040604@chiaraquartet.net>
MIME-Version: 1.0
Content-Type: multipart/alternative; 
	boundary="----=_Part_15327_24353743.1196791981623"
References: <4731278C.8020301@chiaraquartet.net>
	 <52dbac0f0712040809v64da917cic9aa803f9800f49b@mail.gmail.com>
	 <475580D5.1010903@chiaraquartet.net>
	 <52dbac0f0712040900o5dc80b26keca60ef841843fd1@mail.gmail.com>
	 <47558C21.7040604@chiaraquartet.net>
Subject: Re: [PHP-DEV] ignored patches
From: malterisio777@gmail.com ("Martin Alterisio")

------=_Part_15327_24353743.1196791981623
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

2007/12/4, Gregory Beaver <greg@chiaraquartet.net>:
>
> Martin Alterisio wrote:
> > 2007/12/4, Gregory Beaver <greg@chiaraquartet.net
> > <mailto:greg@chiaraquartet.net>>:
> >
> >     Martin Alterisio wrote:
> >     > 1) Why is performance relevant to whether namespaces are
> >     implemented one per
> >     > file or many per file?
> >
> >     Because there is a performance difference between code in separate
> >     files
> >     and the same code in a single file.
> >
> >     [snip]
> >
> >
> > As I said to Roman: Sorry but that still doesn't answer my question.
> > That answer the question of "why use bundling?".
> Yes it does, perhaps you misunderstand the answer?  Let me rephrase:
> because it is faster to bundle in some circumstances, and in some
> circumstances significantly faster than any other possible optimizations.


I just want to have an objective view of the problem. Right now I could care
less about namespaces being one per file, many per file, called packages,
namespaces, zendspaces or whatever. The only thing I care right now is that,
as a fellow php developer, I want to be sure that the ones running the show
have objective information to take a decision.

The only thing I see lately in this debate is performance comparison of
bundled and unbundled code. How's that relevant to decide whether namespaces
should be one per file or many per file?

Answering "bundling increases performance and performance is better" does
not answer this question. If it was just about performance we could just go
back to writing CGIs in C.

As I see it now, the objection to how namespaces are implemented is biased
towards the specific needs of a group of developers. Shouldn't you try first
if you can adjust your requirements to the new features rather than adjust
the language to your requirements?

> Also, what you exposed shows that the bundling process that you're
> > currently using needs to be updated to take in consideration the
> > inclusion of namespaces in PHP.
> see my reply to your other message.  You're wrong, it's not possible to
> reliably bundle files containing namespace/import statements as
> currently implemented.
>

It's also not possible to reliably bundle files even if you could have
multiple namespaces declarations as, correct me if I'm wrong, import
statements affect the whole file, there is no way to "unimport", a name
clash could still occur.

------=_Part_15327_24353743.1196791981623--