Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:8736 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 72460 invoked by uid 1010); 24 Mar 2004 08:17:35 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 72334 invoked from network); 24 Mar 2004 08:17:34 -0000 Received: from unknown (HELO basiczlager.backendmedia.com) (195.75.116.242) by pb1.pair.com with SMTP; 24 Mar 2004 08:17:34 -0000 Received: from localhost (localhost [127.0.0.1]) by basiczlager.backendmedia.com (Postfix) with ESMTP id 8F16482C36; Wed, 24 Mar 2004 09:17:38 +0100 (CET) Received: from basiczlager.backendmedia.com ([127.0.0.1]) by localhost (basiczlager [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 02876-04; Wed, 24 Mar 2004 09:17:33 +0100 (CET) Received: from backendmedia.com (p213.54.205.27.tisdip.tiscali.de [213.54.205.27]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by basiczlager.backendmedia.com (Postfix) with ESMTP id 388C682C34; Wed, 24 Mar 2004 09:17:32 +0100 (CET) Message-ID: <40614397.7030507@backendmedia.com> Date: Wed, 24 Mar 2004 09:15:19 +0100 Organization: BackendMedia GbR User-Agent: Mozilla Thunderbird 0.5 (Windows/20040207) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Rasmus Lerdorf Cc: Marcus Boerger , internals@lists.php.net References: <198200203812.20040324004817@marcus-boerger.de> In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at backendmedia.com Subject: Re: [PHP-DEV] sqlite's oo api From: smith@backendmedia.com (Lukas Smith) Rasmus Lerdorf wrote: > ramifications of such a change. For example, how many PEAR packages might > we break with this? Are any of them perhaps even in the php5 tarball > itself? I know this is just an example, but just to clarify: PEAR is currently taking a bit of a wait and see approach with php5 for obvious reasons. We are mainly looking at the BC breaks atm, so there are really few packages that have moved to php5 only (afaik only PHPUnit2 and SOAP2, which both havent reached a stable state yet). Beyond that the biggest problem I can see PEAR facing with php5 are non studlyCaps API's since then we have to wrap those API's even if we actually just want to extend them, since our CS is studlyCaps. Beyond that I want to make clear that I am in no position to vote on anything on internals@ due to my lack of direct involvement with the php source itself. regards, Lukas Smith