Re: What is our definition of a "Backward Compatibility Break"

Hi! > Change in phpinfo related stuff are minor. Adding a notice or warning > is minor or irrelevant. Changing return values (like suddenly I'm not sure I agree about warning/notice. Depends if it's a clear bug - either in our code (like, opening non-existing file produces warning but opening it with another function does not) or in user code (like giving wrong parameters to a function or calling it in a clearly wrong context). If it's not than it actually may disturb working code so we have to be careful. E.g., PHPUnit unit tests will drop out on any unexpected warning. Some applications would do the same due to their error handler structure. -- Stanislav Malyshev, Software Architect SugarCRM: http://www.sugarcrm.com/ (408)454-6900 ext. 227