Re: Breaking BC / Changing API / Deprecating
| From: | Greg Beaver | Date: | Wed, 20 Jul 2005 05:12:28 +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-38778@lists.php.net to get a copy of this message | ||
Joe Stump wrote:
Um, the point is that your code will continue to work happily with Foo_Bar. You never need to change it, unless you want the new features of Foo_Bar2. In this case, you can do a text search for Foo_Bar and replace it with Foo_Bar2 (carefully) and Foo/Bar.php to Foo/Bar2.php, and then use the new features. In the system you're describing, the application would suddenly cease to function should the user stupidly upgrade to Foo_Bar 2.0. *THAT* is a BC break. Greg3) 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.