On Dec 6, 2007 12:05 PM, Gergely Hodicska <[EMAIL PROTECTED]> 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 -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
