Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:15976 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 95027 invoked by uid 1010); 15 Apr 2005 17:49:32 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 95012 invoked from network); 15 Apr 2005 17:49:32 -0000 Received: from unknown (HELO pb1.pair.com) (127.0.0.1) by localhost with SMTP; 15 Apr 2005 17:49:32 -0000 X-Host-Fingerprint: 64.233.184.198 wproxy.gmail.com Linux 2.4/2.6 Received: from ([64.233.184.198:51766] helo=wproxy.gmail.com) by pb1.pair.com (ecelerity 1.2.12rc1 r(5476:5477)) with SMTP id F2/15-45330-CAEFF524 for ; Fri, 15 Apr 2005 13:49:32 -0400 Received: by wproxy.gmail.com with SMTP id 49so709460wri for ; Fri, 15 Apr 2005 10:49:26 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=r+2K2duKKYj0xoXEyXe1GY/bHDKYqEgkpvPkO3T/23m8v1Zp90CYuHHxY0WaNgliSIcFtlasoY/cNpJtagmOWEJaRHO6U0ORTqBlrgZPFNb1Zs0kiTPm4x2aDFxNrEdTiLnJu4sCcC2+Qwf+mLVWjCPHqMGYjAIsQ7v3yTXhsj4= Received: by 10.54.55.25 with SMTP id d25mr18043wra; Fri, 15 Apr 2005 10:49:15 -0700 (PDT) Received: by 10.54.17.61 with HTTP; Fri, 15 Apr 2005 10:49:14 -0700 (PDT) Message-ID: <6ec19ec70504151049617bba8e@mail.gmail.com> Date: Fri, 15 Apr 2005 13:49:15 -0400 Reply-To: Paul Reinheimer To: internals@lists.php.net In-Reply-To: <20050415170331.46096.qmail@lists.php.net> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <20050415170331.46096.qmail@lists.php.net> Subject: Re: [PHP-DEV] Yet Another Stupid Question: Why Bother with Compatibility? From: preinheimer@gmail.com (Paul Reinheimer) The advantage of maintaining reverse compatibility is that it helps encoura= ge people to upgrade. Many more people would have many more concerns if the 4 -> 5 upgrade broke programs using depreciated practices. ISPs and hosting companies in particular would be extremely reluctant to upgrade as it would promptly result in several (hundred?) support tickets asking "My code worke= d yesterday, now it doesn't! What did you do?!!!!!?!!". I will be honest, I've written the majority of my code in the last year, but am I 100% positive that I'm not using anything that was marked as depreciated in PHP 4? Absolutely not. For all I know I might be using some deprecated func= tion in some arcane, rarely used administrative include file hiding somewhere in= the depths of my file system. Everything would apparently keep working when I upgraded, and even for days/weeks after the fact. Then boom, one day someth= ing important brakes, and I have no idea why. I would assume that the percentage of people willing to upgrade is directly proportional to the percentage of BC. just my 2cents (canadian). paul On 4/15/05, GamblerZG wrote: > Maintaining compatibility between different major versions of PHP must > be extremely hard. Maybe that is obvious, but I do not quite understand > why developers do it. Why PHP 5 has to understand deprecated syntax of > PHP 4? I mean, if someone needs to execute old scripts, they can always > use old engine. >=20 > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php >=20 >=20 --=20 Paul Reinheimer Zend Certified Engineer