4 ms·

I don't agree the breaking BC is a bullshit statement. We all saw how long it took for the majority of PHP users to be able to use PHP 5 due to hosts not upgrad

I don't agree the breaking BC is a bullshit statement. We all saw how long it took for the majority of PHP users to be able to use PHP 5 due to hosts not upgrading. If all code breaks then we'll end up with two branches of PHP for the developers to maintain for very, very long. The question of whether or not to break BC basically boils down to doomed if you do; doomed if you don't.

nathan_long 13y ago
Yep. Notice how long it's taking Python programmers to change major versions.
mgkimsal 13y ago
I agree with the idea, but there's room for a coordinated effort nonetheless. From a naming consistency standpoint on strpos vs str_replace, for example, we could have a new set of function names aliased to the old, and let those run in parallel for a while, with deprecation notices on use of the old ones. Ugly? Perhaps, but it's a way forward to standardize the internal function naming without breaking BC overnight.
- delian66 13y ago
  The PHP team does this already ... it is a slow process, but I think in the right direction: http://php.net/manual/en/migration53.deprecated.php http://php.net/manual/en/migration53.deprecated.php
  - mgkimsal 13y ago
    Not quite for the same reasons it seems. But, since they already do do this, why not take on standardizing function spacing? strpos would become str_pos, etc.
    - wvenable 13y ago
      Because there just isn't that much value in it.
laumars 13y ago
That's why you issue depreciation warnings over the lifetime of the next major release but support both naming conventions rather than just nuke the old function names.