Hi! > Well yes, but the interface description currently says that it'll return > a value of some unspecified type. That's what omitting the return type > declaration does.
No, it doesn't do that. It doesn't do anything - it just provides no information. If you rely on it to return something, then the interface should be modified accordingly, or the documentation should be. > I don't think extension can be harmless. People will unintentionally > rely on such added behaviour unless you force them not to. While it's If people rely on behavior that is not defined as part of interface, they are using interface wrong. void would not help them there - just saying "void" does not prevent anybody from still violating the rules and trying to use the return value. > not ideal, programmers do not look up the documentation and carefully > read it every time they use a function. They will make mistakes. Surely they will. But adding void does not help avoiding them - if they won't look up the functions they are calling, they wouldn't know it is "void" and thus would feel free to use its return value. -- Stas Malyshev smalys...@gmail.com -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
