Re: Declaration of Bar::__construct() must be compatible
| From: | Derick Rethans | Date: | Fri, 27 Feb 2004 15:13:39 +0000 |
| Subject: | Re: Declaration of Bar::__construct() must be compatible | ||
| References: | 1 2 3 4 5 6 7 8 9 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-8229@lists.php.net to get a copy of this message | ||
On Fri, 27 Feb 2004, Andi Gutmans wrote:
> At 14:13 27/02/2004 +0100, Derick Rethans wrote:
> >On Fri, 27 Feb 2004, Andi Gutmans wrote:
> >
> > > d) Last problem is that using E_STRICT is not a good idea because we find
> > > this problem at compile-time and the error_reporting might not be set yet.
> >
> >The INI system is 'booted' before the script is compiled, so I doubt
> >that this is a problem.
>
> Yeah but people are used to setting the error_reporting from prepend's or
> at the beginning of the script. But you know what, I guess we can live with
> this because I see a few E_WARNINGS at the compile stage. So I guess we
> could go with E_STRICT for people who want to get the warning (and the
> script will still run).
> The question is if we should ignore constructors from this check. I think
> we should but one person here thought we shouldn't.
I think we should too.
> That could work too. So in zend.ze2_compatibility_mode we'd do an E_STRICT
> and otherwise an E_WARNING? I think it's even OK if we just go with
> E_STRICT in all cases.
yeah, that sounds better to me too.
Derick