Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:26225 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 51794 invoked by uid 1010); 24 Oct 2006 12:44:25 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 51779 invoked from network); 24 Oct 2006 12:44:25 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 24 Oct 2006 12:44:25 -0000 Authentication-Results: pb1.pair.com smtp.mail=rquadling@googlemail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=rquadling@googlemail.com; sender-id=pass; domainkeys=good Received-SPF: pass (pb1.pair.com: domain googlemail.com designates 64.233.166.177 as permitted sender) DomainKey-Status: good X-DomainKeys: Ecelerity dk_validate implementing draft-delany-domainkeys-base-01 X-PHP-List-Original-Sender: rquadling@googlemail.com X-Host-Fingerprint: 64.233.166.177 py-out-1112.google.com Linux 2.4/2.6 Received: from [64.233.166.177] ([64.233.166.177:23293] helo=py-out-1112.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id C8/F6-30135-6AA0E354 for ; Tue, 24 Oct 2006 08:44:23 -0400 Received: by py-out-1112.google.com with SMTP id t32so159217pyc for ; Tue, 24 Oct 2006 05:44:20 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=googlemail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=W+S56ZNhqlW0t0U9frZkkwy9K86u4zk5BLI2FeOmY/E87K0EfL3iMpp0X0BBtTaQbJUvUFWv70q/jvGLMoU4gj5S/+nR4LScVvhvs4fD23Mq15f6F2zEKOgByTwuZUZAZoQqAZ7+uKmTPXTZNh5E4iswczn/zXzWeA95azCrdPs= Received: by 10.35.8.13 with SMTP id l13mr8765727pyi; Tue, 24 Oct 2006 05:44:19 -0700 (PDT) Received: by 10.35.97.14 with HTTP; Tue, 24 Oct 2006 05:44:19 -0700 (PDT) Message-ID: <10845a340610240544n2659bc7ra5cbaf805c422f92@mail.gmail.com> Date: Tue, 24 Oct 2006 13:44:19 +0100 Reply-To: RQuadling@GoogleMail.com To: "Lukas Kahwe Smith" Cc: "Marcus Boerger" , internals@lists.php.net In-Reply-To: <453E0A06.1020802@php.net> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <1485570655.20061023210857@marcus-boerger.de> <10845a340610240139q570dddf1t6a50a7d0309803f2@mail.gmail.com> <453E0A06.1020802@php.net> Subject: Re: [PHP-DEV] [RFC] E_DEPRECATED From: rquadling@googlemail.com ("Richard Quadling") On 24/10/06, Lukas Kahwe Smith wrote: > Richard Quadling wrote: > > > +1 - As an aside, it would be extremely useful to have the PEAR > > classes marked as NON strict (in some way) until they are. I know this > > is outside of the core, but using E_STRICT already means you have to > > toggle off E_STRICT for PEAR. MAYBE STRICT (e.g. strict class PEAR > > {...}) as a new keyword for a class, just so that you know that it IS > > strict (or at least expecting to be). > > heh .. no that would not be useful .. it would be lying. PEAR already > has decided on an RFC that will mandate PHP5 only for new packages soon. > Also PEAR mandates E_STRICT compliance for PHP5 only packages. So time > will fix this issue. Ah. Oh. Excellent. Didn't know that. Thank you. (Balancing ... balancing ...) -- ----- Richard Quadling Zend Certified Engineer : http://zend.com/zce.php?c=ZEND002498&r=213474731 "Standing on the shoulders of some very clever giants!"