Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:26209
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain php.net from 140.211.166.39 cause and error)
DomainKey-Status: good
DomainKey-Signature: q=dns; a=rsa-sha1; c=nofws;
	s=mx; d=php.net;
	h=From:Subject:To:Date;
	b=JrIA8j+YBnAZAJ4sFEOqrlcFLth+d6/M+kxtSCTK0RKo7aZVsBYqAmXx4piD2bdZ
	AUs/xaa+hyPU2Aocgmr6PONTWwa0ei8M4sDuQVG7vjxfMpQ7joJVc1NUFZx3dE4q
Message-ID: <453D3C1D.4040707@php.net>
Date: Tue, 24 Oct 2006 00:03:09 +0200
Organization: PHP.net
User-Agent: Thunderbird 1.5.0.7 (Windows/20060909)
MIME-Version: 1.0
To: Derick Rethans <derick@php.net>
CC: Marcus Boerger <helly@php.net>, 
 PHP Developers Mailing List <internals@lists.php.net>
References: <1485570655.20061023210857@marcus-boerger.de> <Pine.LNX.4.62.0610232124440.30333@localhost>
In-Reply-To: <Pine.LNX.4.62.0610232124440.30333@localhost>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] [RFC] E_DEPRECATED
From: edink@php.net (Edin Kadribasic)

Derick Rethans wrote:
>>   . E_STRICT any rule that reflects common strict standards, like OOP theory
>>     that is considered harmless if not followed. For example the combination
>>     'abstract static' makes no sense in said theory but doesn't put our zend
>>     engine in an unstable state.
> 
> +1, but then we should also expand this to include:
> 
>     - setting object variables without declaring them
>     - auto-creating objects of stdclass on the fly
>     - and other things that you *should* (not) do
> 
>     These can be added later ofcourse, doesn't have to be directly in 
>     5.2.0, however that would probably be better.

I'm -1 on expanding strictness to this. I don't understand why you
should not do this? Writing mydb_fetch_object() becomes impossible in
userspace if we go this far. It would also make any legal use of
stdClass impossible.

Edin