Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:62937 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 16628 invoked from network); 10 Sep 2012 23:12:06 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 10 Sep 2012 23:12:06 -0000 Authentication-Results: pb1.pair.com smtp.mail=smalyshev@sugarcrm.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=smalyshev@sugarcrm.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain sugarcrm.com designates 67.192.241.163 as permitted sender) X-PHP-List-Original-Sender: smalyshev@sugarcrm.com X-Host-Fingerprint: 67.192.241.163 smtp163.dfw.emailsrvr.com Linux 2.6 Received: from [67.192.241.163] ([67.192.241.163:46817] helo=smtp163.dfw.emailsrvr.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 5A/C3-26944-5C37E405 for ; Mon, 10 Sep 2012 19:12:05 -0400 Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp26.relay.dfw1a.emailsrvr.com (SMTP Server) with ESMTP id 2AB9B8023B; Mon, 10 Sep 2012 19:12:03 -0400 (EDT) X-Virus-Scanned: OK Received: by smtp26.relay.dfw1a.emailsrvr.com (Authenticated sender: smalyshev-AT-sugarcrm.com) with ESMTPSA id D5E0A80138; Mon, 10 Sep 2012 19:12:02 -0400 (EDT) Message-ID: <504E73C2.9030004@sugarcrm.com> Date: Mon, 10 Sep 2012 16:12:02 -0700 Organization: SugarCRM User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:15.0) Gecko/20120824 Thunderbird/15.0 MIME-Version: 1.0 To: Pierre Joye CC: jpauli , PHP Internals References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] What is our definition of a "Backward Compatibility Break" From: smalyshev@sugarcrm.com (Stas Malyshev) 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