Hello Andi, I have to strongly disagree with your ifsetor() comment. the use for ifsetor is in no way eliminated with filtering.
I write very clean code and have taught all my developers to write very clean code. We run the latest stable PHP version with maximum error reporting. We do this so we can have more secure code with fewer logic errors. However, running in E_STRICT makes life rather miserable for simple things such as accessing any array key that may or may not have been included. I'm finding myself having the need for the ifsetor() construct in all areas of programming - not just in _POST or _GET. Even though you don't see yourself using it much, there are many developers on this list who DO see the use for it, and there are countless developers off this list who don't even know about it, but would find it useful for migrating to E_ALL | E_STRICT error reporting. If there was any way to accommodate this with userland PHP code, I would have already done it. However it is an engine level function that has to be added to the core of PHP. +ALot Thanks. -- Best regards, Jason mailto:[EMAIL PROTECTED] Sunday, June 5, 2005, 3:13:52 PM, you wrote: >>4) I still want the ifsetor operator since it is very helpfull and again >>simplifies a lot of things. AG> I don't think ifsetor() shortcut is a big deal nor needed in PHP. I've said AG> it numerous times. Once we have a filtering API there will be even less AG> times where it will be applicable. Write an extra 10 characters or so... AG> Andi -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
