Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:33814
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.198.188 as permitted sender)
DomainKey-Status: bad
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=CRTZde6cEHlYtmpzy/OIG0ZSlWnzV1zQW5WVQc4bzHKE1HMz/fXbN9aXOqWwE8Ypj33cUywqGvVIoSOb74fMDUbeAT8OnpDNLuX48UIzoi/Io+Y5tJSUDPQiJG6D3/gQk1PP1KyL3e/wU8sUOtbciZt9IrXbD71VXDvNI1PE/A4=
Message-ID: <fe05d1540712061210q69194be6ucece37f5f7e2901b@mail.gmail.com>
Date: Thu, 6 Dec 2007 21:10:22 +0100
To: "Gergely Hodicska" <felho@avalon.aut.bme.hu>
Cc: "internals@lists.php.net" <internals@lists.php.net>
In-Reply-To: <4757D783.90705@avalon.aut.bme.hu>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <4731278C.8020301@chiaraquartet.net> <4731F977.4080502@zend.com>
	 <4753B087.4020206@chiaraquartet.net> <4754807B.80408@zend.com>
	 <4754A1EE.1090405@avalon.aut.bme.hu> <47559A4A.70408@zend.com>
	 <58308.81.182.142.127.1196806917.squirrel@avalon.aut.bme.hu>
	 <4755FE85.1040905@zend.com> <4757D783.90705@avalon.aut.bme.hu>
Subject: Re: [PHP-DEV] ignored patches
From: pierre.php@gmail.com (Pierre)

On Dec 6, 2007 12:05 PM, Gergely Hodicska <felho@avalon.aut.bme.hu> wrote:
> Hi!
>
>
> > Yes, that's my point - 3X faster include opcode is not 3X faster code.
> > Of course if you do this opcode a lot of times, it would be somewhat
> > slower than if you do this opcode just one time. However, the question
> > is how it would influence the whole application?
> I didn't say that the code will be 3x faster, the main point is that you
> can gain considerable performance improvement. Of course this is only
> one factor of optimization, but not a negligible one.
>
> http://www.schlossnagle.org/~george/talks/ZendPerf.pdf
>
> > I don't guess. Why guess if I can ask you?
> Maybe you should presume that the other is not a dummy (of course it
> could happen :)). (I tried the test more time and I get always this
> results.)

It is not about being stupid/dummy/whatever. The problem and no matter
how good/bad you are is to have to worry about such things with a high
level languages. include/require and their brother
include_once/require_once have rocked for simple code inclusion in our
all-in-one scripts or templates. But they are a pain to use as package
(like "import DB.* as myDB").

As far as I remember, PHP did not want such concepts of package. I
think it is pretty much what everyone is looking for, to supercede
include/require in php libraries/apps (not in templates) and to
fantastically improved our """namespaces""" (which are not namespaces
anyway but basic aliases).
</fud>

--Pierre