Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:19318 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 2780 invoked by uid 1010); 1 Oct 2005 15:37:33 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 2731 invoked from network); 1 Oct 2005 15:37:33 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 1 Oct 2005 15:37:33 -0000 X-Host-Fingerprint: 81.169.182.136 ajaxatwork.net Linux 2.4/2.6 Received: from ([81.169.182.136:51833] helo=strato.aixcept.de) by pb1.pair.com (ecelerity 2.0 beta r(6323M)) with SMTP id DB/12-54476-947AE334 for ; Sat, 01 Oct 2005 11:12:09 -0400 Received: from [192.168.1.3] (dslb-082-083-226-200.pools.arcor-ip.net [82.83.226.200]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by strato.aixcept.de (Postfix) with ESMTP id 0B0A435C36E; Sat, 1 Oct 2005 17:12:39 +0200 (CEST) Date: Sat, 1 Oct 2005 17:12:21 +0200 Reply-To: Marcus Boerger X-Priority: 3 (Normal) Message-ID: <61717588.20051001171221@marcus-boerger.de> To: Pierre Cc: internals@lists.php.net In-Reply-To: <20051001170401.38d94e3d@localhost.localdomain> References: <20051001162402.4dc07ea1@localhost.localdomain> <1528716499.20051001164847@marcus-boerger.de> <20051001170401.38d94e3d@localhost.localdomain> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] Re: phar and e_strict From: helly@php.net (Marcus Boerger) Hello Pierre, Saturday, October 1, 2005, 5:04:01 PM, you wrote: > On Sat, 1 Oct 2005 16:48:47 +0200 > helly@php.net (Marcus Boerger) wrote: >> Hello Pierre, >> >> Saturday, October 1, 2005, 4:24:02 PM, you wrote: >> >> > On Sat, 1 Oct 2005 16:17:19 +0200 (CEST) >> > derick@php.net (Derick Rethans) wrote: >> >> >> >> 1. not modify any error reporting setting >> >> > We have to modify it as the underlying code is not php5 _only_ but >> > have to work for both php5 and php4. >> >> >> 2. PHP 5.1 compatible code. >> >> > It is compatible, or do you mean E_STRICK compatible? >> >> You should face reality that php 5 is a bit different than php 4. > I do know that, I did explain my opinions about having PEAR bundled by > default in 5.1+ and so on. But other php developers seem to fully > disagree with me on this topic, as many PEAR developers, nothing more I > can do. >> Many of the things changed in php 5 were made to support exactly pear >> development but pear is absolutley ignoring it. > As PEAR 1.4 _has_ to be compatible with 1.x, we did not ignore the > changes. But we cannnot drop php4 support > or maintain 2 code bases. Then you don't suit php development and should get stripped out - end of discussion - do what ever you want then! >> Why can't at least the things that shall be shipped in 5.1 fashion - >> especially since you're doing part of it in a way only 5.1 can serve >> anyway. > I do not get this sentence, can you elaborate? You need to provide a 5+ version of core pear components so that we cn ship those with 5.1. Best regards, Marcus