On his blog today, Pierre has a comment about the new PHP 5.0.5 release - and how a "relatively important BC break" has been made.

5.0.5 seems to have the fix for the famous memory corruption problem (or at least part of the fix). What does that mean for the lambda user or the company having thousands of thousands of lines of code to review and "fix"?

That means to delay the update and leave possible security problems open.

I know it's hard for the development team to work around every issue that might cause a BC break, and making those changes can make for headaches of users down the line - but I'm left wondering if it's worth it. I almost want to side with the forward-thinking at this point in PHPs development. I know there's a lot of things that are going to change in the near future, and I'd rather the developers work hard on getting those changes made than worry about features/uses that may be a bit more outdated...