You can ask about a question. You can even try to improve the
performance of a function. But at the end of the day unless you can
come up with something that will do what the PHP community at large
expects *and* it is faster it's not going to happen.
How exactly PHP community at large supposed
GamblerZG wrote:
You can ask about a question. You can even try to improve the
performance of a function. But at the end of the day unless you can
come up with something that will do what the PHP community at large
expects *and* it is faster it's not going to happen.
How exactly PHP
I do not question usefulness of include_once(). In fact, currently I'm
developing application that might use it exactly the way you described.
There are many API functions in several files, and there are cases when
I do not need all of them. That is exactly why I am concerned with it's
Why include_once() is doing some fancy logic, which nobody needs?
Why array_shift() re-indexes arrays?
Why 2 simple string comparisons are slower than one preg_match()?
Why microtime(TRUE) returns only fraction of real time that is smaller
than 1?
Why microtime() does not return float in the
[snip]
Why include_once() is doing some fancy logic, which nobody needs?
Why array_shift() re-indexes arrays?
Why 2 simple string comparisons are slower than one preg_match()?
Why microtime(TRUE) returns only fraction of real time that is smaller
than 1?
Why microtime() does not return float in
Why don't you RTFM?
There is nothing in manual that answers any of those questions.
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
[snip]
Why include_once() is doing some fancy logic, which nobody needs?
Why array_shift() re-indexes arrays?
Why 2 simple string comparisons are slower than one preg_match()?
Why microtime(TRUE) returns only fraction of real time that is smaller
than 1?
Why microtime() does not return float in
On Tue, April 5, 2005 11:44 am, GamblerZG said:
Why include_once() is doing some fancy logic, which nobody needs?
Obviously somebody needed it, or they wouldn't have written it!
If you don't need it, you can roll your own in about 10 seconds, or you
could simply *NOT* use include_once and
Jay Blanchard wrote:
[snip]
Why include_once() is doing some fancy logic, which nobody needs?
I need it. If you don't need it, don't use it.
Why array_shift() re-indexes arrays?
Because most people *expect* it to behave that way.
Why 2 simple string comparisons are slower than one
What fancy logic? And why does no one need it?
I'm referring to this:
http://archives.devshed.com/a/ng/557-22943/
Now surely you can RTFM and find more answers. If you disagree with the
way that some things work you have a couple of options;
a. Contact the PHP development group and explain
A sample use:
[...]
'include_once' allows me to lazy load -- and thus optimize my
application. Sure, it may be a slight performance hit -- but not nearly
that of loading the files in question.
I do not question usefulness of include_once(). In fact, currently I'm
developing application that might
11 matches
Mail list logo
