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 -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
