Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:26555
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain zend.com designates 212.25.124.162 as permitted sender)
Message-ID: <455982A4.5030308@zend.com>
Date: Tue, 14 Nov 2006 00:47:32 -0800
Organization: Zend Technologies
User-Agent: Thunderbird 1.5.0.8 (Windows/20061025)
MIME-Version: 1.0
To:  RQuadling@GoogleMail.com
CC: Antony Dovgal <antony@zend.com>, php-dev <internals@lists.php.net>
References: <4558E5E7.5040809@zend.com>	 <10845a340611140024l4902ea09q600a43c5018e819c@mail.gmail.com>	 <45597FA6.90808@zend.com> <10845a340611140041p4cc13daft875f4fc99f1c8d19@mail.gmail.com>
In-Reply-To: <10845a340611140041p4cc13daft875f4fc99f1c8d19@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] fgets()/fgetss() BC break in HEAD
From: stas@zend.com (Stanislav Malyshev)

Richard Quadling wrote:
> Just because it has always done it doesn't mean it always will. That's
> what BC's are about.

BC, as far as I know, is "backwards compatibility". It is *exactly* 
about "it has always done so and it always will". And unless there's a 
*very* good reason not to do it, so it should be.

> If this was to be a BC, having it mid version is not a good idea.
> Maybe for V6 where a whole LOAD of things are going to change, making

So let's add one more, just for the fun of it?

> it another part of the clean up process would be a better option.

There's noting more "clean" in new way than in old way - it's a matter 
of convention. If might be not an ideal one, but having two conventions 
is much worse than having one non-ideal convention - you can easily deal 
with latter and you will really hate the guts of the language developers 
for the former, once your scripts start to break.


-- 
Stanislav Malyshev, Zend Products Engineer
stas@zend.com  http://www.zend.com/