Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:26631 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 30154 invoked by uid 1010); 15 Nov 2006 21:24:58 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 30130 invoked from network); 15 Nov 2006 21:24:57 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 15 Nov 2006 21:24:57 -0000 Authentication-Results: pb1.pair.com smtp.mail=stas@zend.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=stas@zend.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain zend.com designates 212.25.124.162 as permitted sender) X-PHP-List-Original-Sender: stas@zend.com X-Host-Fingerprint: 212.25.124.162 mail.zend.com Linux 2.5 (sometimes 2.4) (4) Received: from [212.25.124.162] ([212.25.124.162:5964] helo=mail.zend.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 6B/6A-53553-9858B554 for ; Wed, 15 Nov 2006 16:24:28 -0500 Received: (qmail 21713 invoked from network); 15 Nov 2006 21:22:57 -0000 Received: from office.zend.office (HELO ?127.0.0.1?) (192.168.16.109) by internal.zend.office with SMTP; 15 Nov 2006 21:22:57 -0000 Message-ID: <455B8589.8050306@zend.com> Date: Wed, 15 Nov 2006 13:24:25 -0800 Organization: Zend Technologies User-Agent: Thunderbird 1.5.0.8 (Windows/20061025) MIME-Version: 1.0 To: Sara Golemon CC: internals@lists.php.net References: <455B80F8.9010402@php.net> In-Reply-To: <455B80F8.9010402@php.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] fgets()/fgetss() BC break in HEAD From: stas@zend.com (Stanislav Malyshev) > Sorry, I meant to say "Noone with an IQ higher than twelve is relying on > this." PHP Developer 1: Let's change functionality for some widely-used function and break BC, because we can and it is so much fun! PHP Developer 2: You know, breaking BC is not nice, people really rely on it and try to write code which works in all PHP versions... P1: What people, nobody uses this functionality anyway! P2: I think there might be people using it, we have a lot of developers and apps out there now, and the manual explicitly says it works like that, so maybe we should leave it alone? P1: I bet you money nobody uses it! P2: Here are code examples of real applications using it. P1: Those people are dumb, we are smart, so we'll break BC anyway because we can't care for all stupid people reading the manual and expecting PHP to work according to it! They should read the source for PHP version they run and figure the stuff out from the source! P2: So, you say reading manual and programming according to the docs is bad? P1: Ouch, those bureaucrats... OK, if you insist, you got it - we'll change the manual too! P2: But what about BC? P1: If you are too dumb or lazy to reread the manual every week - it's your fault, you are too dumb to use PHP! Go use C where they keep all the stuff back from 70s! What's wrong with this dialogue? >> Or change the docs and the variable name to something other than >> maxchars is a perfect solution. :-) Yes, you only forgot the part about going back in time 10 years and doing it back then :) -- Stanislav Malyshev, Zend Products Engineer stas@zend.com http://www.zend.com/