| The point is that the SOAP (or whatever) library will be interfacing | with code written by others. If those other people use type hints and | it blows up with an E_ERROR, we don't have a nice way to handle this | error and continue serving. | | This *is* a disaster, because we are introducing a feature that appears | to be quite nice at first glance, but causes portability issues with | peoples scripts; for instance; PEAR scripts that use type hints will | immediately be incompatible with a larger application framework. | Therefore, PEAR should not use type hints if it wants to remain | portable.
I am no "novice" programmer, but I don't get where you are going here. How is there a portability problem? You are either calling the method with the right paramaters or you aren't. What am I missing? Brian. dealnews.com -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
