Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:62931 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 626 invoked from network); 10 Sep 2012 19:54:25 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 10 Sep 2012 19:54:25 -0000 Authentication-Results: pb1.pair.com header.from=rasmus@lerdorf.com; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=rasmus@lerdorf.com; spf=permerror; sender-id=unknown Received-SPF: error (pb1.pair.com: domain lerdorf.com from 209.85.212.42 cause and error) X-PHP-List-Original-Sender: rasmus@lerdorf.com X-Host-Fingerprint: 209.85.212.42 mail-vb0-f42.google.com Received: from [209.85.212.42] ([209.85.212.42:63985] helo=mail-vb0-f42.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id BF/41-26944-E654E405 for ; Mon, 10 Sep 2012 15:54:24 -0400 Received: by vbbfs19 with SMTP id fs19so3359672vbb.29 for ; Mon, 10 Sep 2012 12:54:20 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:x-enigmail-version:content-type :content-transfer-encoding:x-gm-message-state; bh=ERXnveRPf6vVnELOC3DFYLaaryqtvPw9hJ7wx3bsppA=; b=a3rWEUhRhthFPxB/z1BHKsNul5ZXBf6sTZqP5toI55PKYPsMZfpxenetFt7qbXshH/ YGHq2wn5CifxqgctOM4uh4Ed6cuA8mUOB38movigEOVvfNPmhDw0ScHUROsTW4i7zCXL XurCffiSpGYZv1gCKBNT42RyEeynSmf/AvdWWhb9MQptnS8pPbfzTJmVnaj0OTxvjc7r 96MGaCTzQo8R+LbQb06ZTQ6Ewfq2GkcsUEWygSc5IF91SiaN0xeVyVs3ss9Rhhwfg1DU 7Rs5vYBztvpMzzRjcpRTKeHqkhdDaIutO7pYET+K6cWV1TwuFBhU/Uuey3i1EnCuAa6I i7mQ== Received: by 10.52.21.82 with SMTP id t18mr17291977vde.66.1347306859696; Mon, 10 Sep 2012 12:54:19 -0700 (PDT) Received: from [192.168.200.148] (c-50-131-44-225.hsd1.ca.comcast.net. [50.131.44.225]) by mx.google.com with ESMTPS id b6sm426670vea.2.2012.09.10.12.54.17 (version=SSLv3 cipher=OTHER); Mon, 10 Sep 2012 12:54:18 -0700 (PDT) Message-ID: <504E4568.4030701@lerdorf.com> Date: Mon, 10 Sep 2012 12:54:16 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20120827 Thunderbird/15.0 MIME-Version: 1.0 To: Anthony Ferrara CC: Pierre Joye , jpauli , PHP Internals References: In-Reply-To: X-Enigmail-Version: 1.4.4 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Gm-Message-State: ALoCoQnQxRl7+fQncpeHiqBHskz8uDhskVvhFZTHpkR2h+6TnuqSKMqsVTLVxp0790bzn/PtUhan Subject: Re: [PHP-DEV] What is our definition of a "Backward Compatibility Break" From: rasmus@lerdorf.com (Rasmus Lerdorf) On 09/10/2012 12:00 PM, Anthony Ferrara wrote: > I chose it for that specific reason. The line is blurry if taken literally > (which many do)... It can't possibly be an absolute rule. If you take it completely literally then we wouldn't be able to fix bugs either. Every change has some effect that may or may not affect users. I know we are mostly geeks here and geeks love structure and rules without exceptions to fall back on so they don't have to think so much and can end arguments simply by pointing at a set of hard rules everyone follows. But this really doesn't work that well in the real world. The real world isn't binary. It is a complicated analog world with many many levels of gray between right and wrong, between minor and major BC break and between peoples' expectations and their personal uses of PHP. -Rasmus