Re: Re: Release process

From:	Andi Gutmans	Date:	Fri, 04 May 2001 00:19:05 +0000
Subject:	Re: Re: Release process
References:	1 2 3 4 5 6 7 8 9 10 11 12 13 14	Groups:	php.dev
Request:	Send a blank email to php-dev+get-53761@lists.php.net to get a copy of this message

At 07:16 PM 5/3/2001 -0500, Andrei Zmievski wrote:

At 03:14 AM 5/4/01 +0300, Andi Gutmans wrote:
Not exactly. No matter if it is set to NULL or unset then isset() will give the same result. And most people use isset() AFAIK.
Whatever the current situation, there needs to be a way to check whether a certain array entry is NULL or not.

If so then we need to make sure that modules like the MySQL module still continue to behave exactly like they used to with isset() and other ways programmers were working. I'm not saying you're wrong. It's probably a good idea but we need to think about the consequences and other changes we might need to make at the same time before breaking stuff. We should probably save all of the NULL stuff for 4.1.x. If we do it the right way we might end up breaking certain scripts. Andi