Re: Latest commit -- depreciation of call_user_method()
| From: | Zeev Suraski | Date: | Fri, 18 May 2001 08:34:53 +0000 |
| Subject: | Re: Latest commit -- depreciation of call_user_method() | ||
| References: | 1 | Groups: | php.dev |
| Request: | Send a blank email to php-dev+get-55733@lists.php.net to get a copy of this message | ||
At 11:21 18/5/2001, Jani Taskinen wrote:
As long as these extensions are in there, I think changing any of their API's is a justification for 4.x release.This is simply not the way we decided to work in. Can it be changed? Sure. Should it be changed? In my humble opinion, no, it shouldn't. The thing I'm trying to state, not very successfully I guess, is that whether it's 4.0.7 or 4.666.3, we should be avoiding API changes as much as at all possible. Sure, sometimes there's just no alternative than to break downwards compatibility, but we should not get into the state of mind that breaking downwards compatibility is ok, as long as you increment some digit in the version number. Zeev