Comments on: PHP: The Problem With is_callable() And __call() http://blog.charcoalphile.com/2009/04/22/php-the-problem-with-is_callable-and-__call/ On Databases, Recovery, Tech Sat, 31 Jul 2010 08:34:28 +0000 http://wordpress.org/?v=2.2.1 By: admin http://blog.charcoalphile.com/2009/04/22/php-the-problem-with-is_callable-and-__call/#comment-3751 admin Thu, 23 Apr 2009 19:20:42 +0000 http://blog.charcoalphile.com/2009/04/22/php-the-problem-with-is_callable-and-__call/#comment-3751 Ugh. Sorry. I should probably stop posting comments when I'm tired. Yeah, you might be able to infer the behavior of is_callable() from the documentation, but thats an assumption. In some places, the documentation doesn't give a good enough description of how things function under certain situations. I've ran into this a couple times before. Ugh. Sorry. I should probably stop posting comments when I’m tired.

Yeah, you might be able to infer the behavior of is_callable() from the documentation, but thats an assumption. In some places, the documentation doesn’t give a good enough description of how things function under certain situations. I’ve ran into this a couple times before.

]]> By: Ian Eure http://blog.charcoalphile.com/2009/04/22/php-the-problem-with-is_callable-and-__call/#comment-3725 Ian Eure Thu, 23 Apr 2009 05:11:43 +0000 http://blog.charcoalphile.com/2009/04/22/php-the-problem-with-is_callable-and-__call/#comment-3725 Not sure I follow you. Assuming you can tell what by looking at the function name? Not sure I follow you. Assuming you can tell what by looking at the function name?

]]> By: admin http://blog.charcoalphile.com/2009/04/22/php-the-problem-with-is_callable-and-__call/#comment-3721 admin Thu, 23 Apr 2009 04:10:14 +0000 http://blog.charcoalphile.com/2009/04/22/php-the-problem-with-is_callable-and-__call/#comment-3721 The documentation should really clarify this. Assuming you can tell by looking at the function name is stupid. There's a lot of little things like this in PHP, that drive me crazy. The documentation should really clarify this. Assuming you can tell by looking at the function name is stupid. There’s a lot of little things like this in PHP, that drive me crazy.

]]> By: Ian Eure http://blog.charcoalphile.com/2009/04/22/php-the-problem-with-is_callable-and-__call/#comment-3719 Ian Eure Thu, 23 Apr 2009 02:15:24 +0000 http://blog.charcoalphile.com/2009/04/22/php-the-problem-with-is_callable-and-__call/#comment-3719 Yeah, I don’t think it’s explicitly documented, but it’s not a stretch to infer it: “__call() is triggered when invoking inaccessible methods in an object context.” “is_callable — Verify that the contents of a variable can be called as a function” I don’t know whether it really qualifies as brain-damaged, but it could be more obvious. The only way around it would be reflection and dynamic instances, so you could look at an object’s methods and replicate them in your object. This would solve it for a Decorator implementation, but I’m sure there are usecases where it’s less optimal. PHP really isn’t flexible enough to support a fully dynamic programming model like that, though. Yeah, I don’t think it’s explicitly documented, but it’s not a stretch to infer it:

“__call() is triggered when invoking inaccessible methods in an object context.”
“is_callable — Verify that the contents of a variable can be called as a function”

I don’t know whether it really qualifies as brain-damaged, but it could be more obvious.

The only way around it would be reflection and dynamic instances, so you could look at an object’s methods and replicate them in your object. This would solve it for a Decorator implementation, but I’m sure there are usecases where it’s less optimal.

PHP really isn’t flexible enough to support a fully dynamic programming model like that, though.

]]>