Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:5557
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
To: internals@lists.php.net
Date: Wed, 19 Nov 2003 16:20:25 +0100
MIME-Version: 1.0
Message-ID: <3FBB9849.10600.EBADF1@localhost>
Priority: normal
In-reply-to: <5.1.0.14.2.20031118235848.0347c9f0@127.0.0.1>
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Content-description: Mail message body
Subject: Re: [PHP-DEV] E_STRICT
From: fb@fbeyer.com ("Ferdinand Beyer")
References: <5.1.0.14.2.20031118235848.0347c9f0@127.0.0.1>

On 19 Nov 2003 at 0:00, Andi Gutmans wrote:

> Hey,
> 
> I added an E_STRICT error level today which purists can use to 
make sure 
> that there scripts are using the latest and greatest suggested 
method of 
> coding (according to what we decide).
> Ideas are things like:
> a) Not using var for member variables but moving to PPP.
> b) Not using is_a but using instanceof.
> 
> If you have any further ideas of stuff which makes sense to add to 
this 
> option let me know. For obvious reasons this will be off by default.
> 
> Andi

What's the difference between E_NOTICE and E_STRICT then?

It would be as easy to trigger errors like
"Notice: Use of deprecated function `is_a`; use `instanceof` instead"

Purists who want to be sure to be coding >The PHP Way< will use 
error_level = E_ALL anyway...

-- 
Ferdinand Beyer
<fb@fbeyer.com>