On Tue, 2003-12-02 at 18:43, Marcus Boerger wrote: > Hello Christian, > > Tuesday, December 2, 2003, 1:14:12 PM, you wrote: > > > Andi Gutmans wrote: > >> E_STRICT will be disabled by default. It is only meant for people who > >> want to be sure that they are using the recommended methods, and that > >> definitely includes not using var. > > > The problem is that it doesn't match the real world. People _are_ using > > PEAR and people _are_ using PHP4. So they simply _can't_ change var to > > public. So E_STRICT is currently way too noisy for them. Hence they'll > > not use it. That's why I think two levels (e.g. E_STRICT for backward > > compatible stuff and E_PEDANTIC for everything) makes sense. Or call it > > E_DEPRECATED and E_STRICT if you want. > > > I for one would love to use E_DEPRECATED if it existed but I can't use > > E_NOTICE (I use uninitialized variables all the time, it's one of the > > main features of PHP for me) or E_STRICT (my code has to work on PHP4). > > I see all your concerns. But from my point of view pear has (of course) the > problem that it is written in php4 and for php4. So PEAR needs to address > the move towards php5 code anyway. An optional E_STRICT would help here > wouldn't it?
PEAR is addressing the move towards PHP 5, but why make it more difficult? We can handle issues at runtime, but during compilation there's not much we can do. What we're trying to avoid is to force every package maintainer to roll PHP 5 specific releases for packages that still support PHP 4. Smooth transition requires that one package at a time can be transitioned, or we would create a dependency mess out of this world. - Stig -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
