At 22:41 19/3/2001, Jason Greene wrote:
>I don't, but I could see that viewpoint where Phil is coming from when he
>talks about the fact
>that functions can end up with 2 different goals, and then when we want to
>enhance them
>we end up with multiple behaviors in a single function and way too many
>option flags.
Generally using functions for two different purposes is a bad idea, but
enhancing functions with additional arguments that extend its functionality
is not too bad. In this case, adding n arguments is perhaps the extension
that makes the most sense for isset(), so we should go with it. Keeping it
with one argument 'for future use' doesn't make much sense in my
opinion. Not any more sense than saying the same thing about some new
argument someone might want to add to it in the future - why not keep it
clean and wait for a 'better' use?
Zeev
--
PHP Development Mailing List <http://www.php.net/>
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]
