> Of course... why do you NEED to know if it's not available or > disabled... the result is the same: you can not use the function. > Sure. But still it is a difference if my code is stable or not. Using an own implementation telling about the disabled state makes it stable. Also code should be performant. It isn't when reading a list of comma seperated function names to a string, afterwards checking if strpos() !== false. I bet ZendEngine knows about all disabled functions, as it should to block the usage. Also I bet it doesn't read the list each time a function gets called, neither per request to some script.
So the list is persistant, access per C code. And the performance and safety is layed down to PHP. IMHO that's more performant, more secure and even more professional. > > If you had read my post, you knew I already do like you telling > > me, but do not agree with this solution, as it is better > > in performance etc. (see my post) to let PHP do so. > > I did read it, I just don't see any point why it is useful. Sorry for the tone, didn't want to be rough. I hope you agree with my statement, now. Regards Dennis -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
