On 3/7/06, Stefan Esser <[EMAIL PROTECTED]> wrote: > > >What is the point of detecting something that does not exist anymore? > > > >It is not a problem to add these checks and errors, only senseless. > > > >What is the reason to do it? PHP6 will require most applications to be > >ported, this problem will be their smallest problem and can be easily > >emulated in userland: > > > > > Forgive me if I am wrong, but MOST PHP applications are not using OOP.
OOP is only a (small) part of the changes. > And I don't see why these applications have to be ported at all. But > once you remove the possibility to detect that these features are turned > off the applications can become insecure. Removing these features do not make application more or less secure. Developers who care about security do not rely on them. > And instead of removing the function set_magic_quotes_runtime() it > should better give a clear FATAL ERROR imho. Otherwise we will have > myriads of bugreports: set_magic_quotes_runtime() or (whatever function > removed) doesn't exist in my PHP anymore. I can take care of these bugs report and bogus them, really not a problem. > Giving the warning that the > script uses a feature that no longer exists and pointing to a document > describing why will save us a lot of work and trouble. It is a migration howto and a documentation problem. Either we keep them or we remove them, but having faked functions are not a good idea, or do we want to keep everything until php10? --Pierre -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
