Just because it has always done it doesn't mean it always will. That's what BC's are about.
If this was to be a BC, having it mid version is not a good idea. Maybe for V6 where a whole LOAD of things are going to change, making it another part of the clean up process would be a better option. On 14/11/06, Stanislav Malyshev <[EMAIL PROTECTED]> wrote:
> It seems utterly ridiculous to return maxlen-1. > > Whilst this is sure as hell a BC, it should work "properly". If I ask > for 10, I want 10. I wouldn't have asked for 10 otherwise. Having to > know the "magic" to get things to work is plainly bad magic. It always returned length-1, manual says length-1, so suddenly in version 5.2.1 it starts returning length instead. And now imagine somebody who tries to use this function in his scripts. He should start adding version checks to each invocation of this function or what? Doesn't seem very nice behavior to me. > Make the break. Deal with it. It was wrong and now it is fixed. Yes, and the way to deal with it is to restore the function to its previous functionality, according to documentation and the way it always worked. If you need exact number, you can always use fread. There's absolutely no reason to break 100% of working scripts (since nobody uses the new semantics and everybody uses the old) just to satisfy someone's sense of purity. -- Stanislav Malyshev, Zend Products Engineer [EMAIL PROTECTED] http://www.zend.com/
-- ----- Richard Quadling Zend Certified Engineer : http://zend.com/zce.php?c=ZEND002498&r=213474731 "Standing on the shoulders of some very clever giants!" -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
