Wez Furlong wrote:
If a method is static, you should only ever call it statically.
Doing any other tricks is just plain wrong.

I dare to disagree. For tool functions it often makes sense to make them statically callable while you still might want to use them in an object instance context respecting the instance's state. It may seem a bit hacky but I like PHP for being dynamic enough to allow this.


Different people use different styles and I wouldn't say "Using exceptions is just plain wrong" even though I don't like them ;-)

If you still want to know the answer, ask the question on the correct
list; what you've asked has nothing to do with hacking on the
internals of PHP in C.

He is asking for a mechanism to properly determine the static/non-static status of a call and I assume he also suggests to add such a mechanism in case it doesn't exist so I think your answer should be less hostile as it concerns internals IMHO.


- Chris

--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php



Reply via email to