On 6/17/05, Sebastian Mendel <[EMAIL PROTECTED]> wrote: > > Besides, the point of E_STRICT seems to be to _enforce_ best practices > > -- and if you care about this matter, considering all members as > > "public" is probably defying the concept anyway. > > but defining all as public doesnt produces any NOTICEs, neither now nor > with the feature we are talking about.
True, but that's not the point. E_STRICT complaints about "var" are a way of saying "erm, you actually didn't put much thought into building this class; you should think about the level of visibility of its members". If you don't want those reminders, forget about E_STRICT. If you leave E_STRICT enabled but try to bypass it (by declaring everything as public for BC) then you didn't understand what E_STRICT is for... -- Nelson Menezes [EMAIL PROTECTED] -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
