Understandably PHP is slower than say C :) Generally I don't think there is need for everything to be a native function, however, that said, when the speed gain and utility are great in comparison to doing it as pure PHP then I think the option should be investigated. The current isset() function fails many developers from what I can see, and I know I've experienced this problem before, and so I think a more appropriate function would be nice. Also I'm sure that native function lookup occurs extremely fast, probably even at compile time, thus i would say as the number of native functions increases the impact becomes less and less on execution time. There are already hundreds of native functions, I can only assume one more would have no bearing or at worst extremely minimal impact, but would provide a useful function to many PHP developers who would find it useful. I'm guessing the current split on this thread is somewhere around 50/50 and so it can't be an entirely useless idea.
Cheers, Rob. On Sat, 2003-08-16 at 18:19, Stefan Walk wrote: > Oh, you meant the first output, nevermind. I /know/ unset() and setting > something null is not the same - as probably everyone on this list. > > As to your "Is not the same" argument: > Doing something in PHP is of course slower as a language feature. But > that's normal. Do you want to have a native function for everything? > -- > Regards, > Stefan Walk > <[EMAIL PROTECTED]> > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > > -- .---------------------------------------------. | Worlds of Carnage - http://www.wocmud.org | :---------------------------------------------: | Come visit a world of myth and legend where | | fantastical creatures come to life and the | | stuff of nightmares grasp for your soul. | `---------------------------------------------' -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
