Re: Breaking BC / Changing API / Deprecating

From: Date: Tue, 19 Jul 2005 19:44:52 +0000
Subject: Re: Breaking BC / Changing API / Deprecating
References: 1 2 3 4 5 6 7  Groups: php.pear.dev 
Request: Send a blank email to pear-dev+get-38744@lists.php.net to get a copy of this message
Joe Stump wrote:
3) Foo_Bar2 will be a different class thus it does not break BC.
Oh please! If I have a major application that relies on Foo_Bar, but want to use Foo_Bar2 because it has some new features I like I have to change *every* require and call to Foo_Bar to Foo_Bar2. If that's not a BC I don't know what is. --Joe
If you want to use the new bells and features you will need to update your code, no matter what. The point is that if you need to upgrade because a security fix was applied your code should not break. If you change the API then you cannot upgrade. BC break means: I have code using Foo_Bar 1.0, if I upgrade to Foo_Bar 1.1 then my code should still run. Removing methods will mean my code will not run. Add as much as you want, just keep the old methods available using the new ones, "the code must run" :) Arnaud.

« previous php.pear.dev (#38744) next »