Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:25813 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 19674 invoked by uid 1010); 25 Sep 2006 07:49:17 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 19659 invoked from network); 25 Sep 2006 07:49:17 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 25 Sep 2006 07:49:17 -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.180 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.180 py-out-1112.google.com Linux 2.4/2.6 Received: from [64.233.166.180] ([64.233.166.180:16963] helo=py-out-1112.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id D8/A3-24622-AF987154 for ; Mon, 25 Sep 2006 03:49:15 -0400 Received: by py-out-1112.google.com with SMTP id c39so2191071pyd for ; Mon, 25 Sep 2006 00:49:12 -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=XEWpZ2IJkJWjGFgGv95FWpZ5bzV+1J/q8a6FgOz0gD0ogb0vJ+he+HrS0+TEaT6BBxNck2ybo23/Vut/DEFtir81aMEK9fyxMSnZHcyEzeu+YD1dy5r9Kq7TA+GNoZkfE5eknIyPUJR67nvuTjm5Dv0qL0rmjkAIY/+GMgHDeuY= Received: by 10.35.113.12 with SMTP id q12mr7235257pym; Mon, 25 Sep 2006 00:49:12 -0700 (PDT) Received: by 10.35.93.18 with HTTP; Mon, 25 Sep 2006 00:49:12 -0700 (PDT) Message-ID: <10845a340609250049v2a68d4f5w6e85f6251721ce38@mail.gmail.com> Date: Mon, 25 Sep 2006 08:49:12 +0100 Reply-To: RQuadling@GoogleMail.com To: "Ron Korving" Cc: internals@lists.php.net In-Reply-To: <47.D2.14982.92F96154@pb1.pair.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <7.0.1.0.2.20060924133501.05254570@zend.com> <47.D2.14982.92F96154@pb1.pair.com> Subject: Re: [PHP-DEV] [VOTE] (was: Parameter checking in 5.2) From: rquadling@googlemail.com ("Richard Quadling") On 24/09/06, Ron Korving wrote: > In this case, wouldn't E_NOTICE make more sense? E_STRICT kind of indicates > that certain behaviour is deprecated, right? I think that's a whole other issue. E_STRICT seems to be used for both errors in coding style (calling static methods from an instance) and for deprecated functionality (mktime(0,0,0,0,0,0)). But there again, some may think that both are just coding style issues. -- ----- Richard Quadling Zend Certified Engineer : http://zend.com/zce.php?c=ZEND002498&r=213474731 "Standing on the shoulders of some very clever giants!"