On 03/08/06, Derick Rethans <[EMAIL PROTECTED]> wrote:
> Err? Code that already works, still works if we make the loose mode the
> default. Anyone who writes new classes can make use of a new strict flag
> however.
Sure, but then that code won't run on older versions of PHP (5.1 f.e.)
anymore, so it is not a good solution.
Currently, if E_STRICT is enabled, you get an E_STRICT non-fatal
notice. Disabling E_STRICT (as you want to NOT be strict with the
code) gives no warning.
So, either userland code is STRICT (in PHP's terms - not
C++/Delphi/Java) and no overloading is allowed and if you try you get
the compile notice OR it is NOT strict and you can overload and get no
notice.
Toggling E_STRICT has no effect at runtime (for this issue) as the
error is raised at compile time.
So, is this problem solved? Very simply, if you want to overload
parameters, don't use E_STRICT.
The issue this brings is toggling E_STRICT on and off at RUNTIME
required? (I suspect that would be a LOT of work).
--
-----
Richard Quadling
Zend Certified Engineer : http://zend.com/zce.php?c=ZEND002498&r=213474731
"Standing on the shoulders of some very clever giants!"
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
