I'd lay money on someone somewhere having something critical relying
on the traditional behavior. IIRC, this came up before and we decided
to preserve the way it worked.
I don't see any need to change this in 6 or any later version.
As crappy as that may be, BC is BC. :-/
--Wez.
On 11/14/06, Sara Golemon <[EMAIL PROTECTED]> wrote:
Antony Dovgal wrote:
> On 11/14/2006 08:26 AM, Andi Gutmans wrote:
>> Sounds like something which indeed isn't worth breaking. Was this
>> intentional?
>
> Sara says it was intentional, that's why I decided to write to the list.
> I don't think such intentional breaks should take place in any PHP version.
>
It was quasi-intentional. The functions needed a lot of changes related
to PHP6 Unicodiness and I implemented "maxchars" to mean "maxchars"
rather than the appearantly expected
"maxcharsbutnotreallycausewedonotwantthelastcharacter".
As I told tony in IRC, I don't care if the behavior gets changed back to
5.2 style, although I don't think this is a BC we need to worry about
keeping. I'll lay money that NOONE is relying on this, and I challenge
any of you to prove me wrong on that count.
If y'all do want maxcharsminusone behavior for the argument, fine, but
rename the arg to something else. maxchars means "I want this many
characters or less", not "I want one less than this many characters{or
less}".
-Sara
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
