Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:16455
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Date: Mon, 6 Jun 2005 13:16:08 -0400
Reply-To: Jason Garber <jason@ionzoft.com>
Organization: IonZoft, Inc.
Message-ID: <1852284679.20050606131608@ionzoft.com>
To: Andi Gutmans <andi@zend.com>
Cc: Marcus Boerger <mail@marcus-boerger.de>, internals@lists.php.net
In-Reply-To: <5.1.0.14.2.20050605120644.033c8a00@localhost>
References: <5.1.0.14.2.20050603203711.028e9140@localhost>
	<5.1.0.14.2.20050603203711.028e9140@localhost>
	<5.1.0.14.2.20050605120644.033c8a00@localhost>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] PHP 5.1
From: jason@ionzoft.com (Jason Garber)

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:jason@ionzoft.com

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