Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:16687 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 31893 invoked by uid 1010); 15 Jun 2005 14:36:39 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 31878 invoked from network); 15 Jun 2005 14:36:39 -0000 Received: from unknown (HELO pb1.pair.com) (127.0.0.1) by localhost with SMTP; 15 Jun 2005 14:36:39 -0000 X-Host-Fingerprint: 212.112.227.169 ipx11223.ipxserver.de Linux 2.4/2.6 Received: from ([212.112.227.169:32768] helo=ipx11223.ipxserver.de) by pb1.pair.com (ecelerity 1.2 r(5656M)) with SMTP id 8C/62-20931-7FC30B24 for ; Wed, 15 Jun 2005 10:36:39 -0400 Received: from localhost (localhost [127.0.0.1]) by ipx11223.ipxserver.de (Postfix) with ESMTP id B7D86DF007B; Wed, 15 Jun 2005 16:37:00 +0200 (CEST) Received: from ipx11223.ipxserver.de ([127.0.0.1]) by localhost (ipx11223 [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 28270-06; Wed, 15 Jun 2005 16:36:57 +0200 (CEST) Received: from [192.168.0.77] (port-212-202-40-148.dynamic.qsc.de [212.202.40.148]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ipx11223.ipxserver.de (Postfix) with ESMTP id B3599DF005A; Wed, 15 Jun 2005 16:36:57 +0200 (CEST) Message-ID: <42B03CF6.9000000@php.net> Date: Wed, 15 Jun 2005 16:36:38 +0200 User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Stanislav Malyshev Cc: internals@lists.php.net References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by somedaemon at backendmedia.com Subject: Re: [PHP-DEV] forward compatibility "public" in 4.4 From: lsmith@php.net (Lukas Smith) Stanislav Malyshev wrote: > LS>>I think its a good idea to have, to make it somewhat possible to prepare for > LS>>the PHP5 E_STRICT world, while still developing PHP4 compatible code. I > LS>>could for example see this help increase the PHP5 adoption inside PEAR, > > Like, PEAR would drop support for PHP 4.3 or it would have two copies of > the code - one with public keyword and one without? Currently PEAR.php requires PHP 4.2. We could eventually (as an intermediate step) move this dep to 4.4, not immediatly. However currently there is a strong trend to create new versions of packages for the main reason of making them E_STRICT compatible. However lets not get too far into the PEAR politics here ;-) Anyways I just wanted to give this as an example. I think its much more useful for independent developers who have more control over their user setups than PEAR. This allows them to make the move less painful and therefore will facilitate rather than prolong the move to PHP5 (which is a good thing). regards, Lukas