Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:26219 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 41311 invoked by uid 1010); 24 Oct 2006 07:06:40 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 41295 invoked from network); 24 Oct 2006 07:06:40 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 24 Oct 2006 07:06:40 -0000 Authentication-Results: pb1.pair.com header.from=derick@php.net; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=derick@php.net; spf=permerror; sender-id=unknown Received-SPF: error (pb1.pair.com: domain php.net from 82.94.239.5 cause and error) X-PHP-List-Original-Sender: derick@php.net X-Host-Fingerprint: 82.94.239.5 jdi.jdi-ict.nl Linux 2.5 (sometimes 2.4) (4) Received: from [82.94.239.5] ([82.94.239.5:39679] helo=jdi.jdi-ict.nl) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 9A/F2-18710-E7BBD354 for ; Tue, 24 Oct 2006 03:06:39 -0400 Received: from localhost (localhost [127.0.0.1]) by jdi.jdi-ict.nl (8.13.7/8.12.11) with ESMTP id k9O76ZDk009198; Tue, 24 Oct 2006 09:06:35 +0200 Date: Tue, 24 Oct 2006 09:05:45 +0200 (CEST) X-X-Sender: derick@localhost To: Edin Kadribasic cc: Marcus Boerger , PHP Developers Mailing List In-Reply-To: <453D3C1D.4040707@php.net> Message-ID: References: <1485570655.20061023210857@marcus-boerger.de> <453D3C1D.4040707@php.net> X-Face: "L'&?Ah3MYF@FB4hU'XhNhLB]222(Lbr2Y@F:GE[OO;"F5p>qtFBl|yVVA&D{A(g3[C}mG:199P+5C'v.M/u@Z\![0b:Mv.[l6[uWl' MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: Re: [PHP-DEV] [RFC] E_DEPRECATED From: derick@php.net (Derick Rethans) On Tue, 24 Oct 2006, Edin Kadribasic wrote: > 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? Because atleast those two points should usually *never* happen in a serious application. They're very often just typoes and make debugging harder. As I know you don't care about that, simply don't turn on E_STRICT... > Writing mydb_fetch_object() becomes impossible in > userspace if we go this far. It would also make any legal use of > stdClass impossible. Yes, but in the "strict" world, there is no legal use for stdClass in the first place. regards, Derick