Hi! > My point is that providing them as "userland implementation" even inside > core would be more interesting than having something magic going on > under the hood.
It certainly may be "interesting", and nobody prevents you from writing a blog or implementing a library doing this. However, it is not the reason to change the core functions of PHP. > Yes, I realize that complete removal would completely kill PHP's > adoption for the next version, so I'm thinking about something like an > ini setting: > > "zeh_legacy_includeh = '/zeh/path/to/old/functions.php';" You're trying to solve a problem that did not exist before you tried to solve it. > Yet this would allow removing a lot of internal functions that were > written just for the sake of it, and move them to something that can be > maintained by a larger userbase. These functions weren't written "just for the sake of it". They were written because people needed it. -- Stanislav Malyshev, Software Architect SugarCRM: http://www.sugarcrm.com/ -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
