Re: How expensive are function_exists() calls?
| From: | mike | Date: | Wed, 04 Mar 2009 19:45:35 +0000 |
| Subject: | Re: How expensive are function_exists() calls? | ||
| References: | 1 2 | Groups: | php.general |
| Request: | Send a blank email to php-general+get-289262@lists.php.net to get a copy of this message | ||
On Wed, Mar 4, 2009 at 4:01 AM, Jochem Maas <jochem@iamjochem.com> wrote:
> ..not an internals question me thinks ... redirecting to generals mailing list
Actually, I do think it is somewhat internals related.
I want to know from the internals/experts angle if this is a good
function to be relying on, or if it is one of those things like the
"@" operator which I've been told is "expensive" and to me is one of
those things to stay away from.
Now if this breaks opcode caches like APC, I will have to find another way.
Also - I write procedural, not OOP. So that won't help here.
Would creating functions such as
output_foo_html()
output_foo_rss()
output_foo_json()
Then depending on the output, using something like this? Would this be
breaking opcode caches as well then?
if(function_exists('output_foo_'.$format)) {
call_user_func('output_foo_'.$format);
} else {
output_foo_html();
}