Re: Re: svn: /php/php-src/branches/ PHP_5_2/configure.in PHP_5_2/ext/standard/file.c PHP_5_2/main/SAPI.c PHP_5_2/main/SAPI.h PHP_5_2/main/rfc1867.c
PHP_5_3/configure.in PHP_5_3/ext/standard/file.c PHP_5_3/main/SAPI.c PHP_5_3/main/SAPI.h PHP_5_3

On Thu, Mar 18, 2010 at 11:37:09PM +0100, Pierre Joye wrote: > While wondering what was the reasoning behind this commit, I came to > the conclusion that we should not do such thing in stable branches and > we should respect something we decided long time ago, to stop to add > bad options which can break PHP ABI or BC in one way or another. It is or maybe at least queue it up in a branch for "BC breaking review", or in a branch where the ABI has already changed? I.e. if at some point you must break the API/ABI, you can then shuttle in the rest of the changes that you would have wanted but had deferred for this reason. > especially important as we all know how distributors tend to deal with > such options. well... it's not like we go making such changes just for the heck of it you know. it's just that keeping cross-distro binary compatibility isn't really a high priority for most open source projects, and it wouldn't be for PHP except for certain non OSS products that depend on it :) but i'm not arguing against the principle of your argument, though. just making some armchair suggestions/commentary. sean