ID: 14285 Comment by: andrew_nefsky at hotmail dot com Reported By: pnh102 at psu dot edu Status: Open Bug Type: Feature/Change Request Operating System: Redhat Linux 7.2 PHP Version: 4.0.6 New Comment:
This is definitely an important issue. Not being able to declare variables creates a debugging nightmare! Previous Comments: ------------------------------------------------------------------------ [2002-11-19 08:06:07] z95kahe at mtek dot chalmers dot se I realy think this is good idea. I've been looking for some tool to do this kind of checks and found none. For small scripts there is no need to have variable declaring but there are for longer multi file, multi developer projects. By making the checks an option we can have both modes available. ------------------------------------------------------------------------ [2001-11-29 11:39:07] [EMAIL PROTECTED] this would only catch read usage of undefined variables, but not assigning values to them see: <?php $typofree = "hallo"; ... $xtypofree = "ooops"; ?> nothing in PHP will warn you that you have a typo in the second assignment, so creating a new variable unintended ... moved to feature requests ... ------------------------------------------------------------------------ [2001-11-29 11:20:18] [EMAIL PROTECTED] set error_reporting to E_ALL, and you'll see all undefined vars. However, it doesn't force the use of it. Derick ------------------------------------------------------------------------ [2001-11-29 11:17:16] pnh102 at psu dot edu Is there a way to make PHP force you to declare variables like "option explicit" in VBScript or "use strict" in Perl? If not, will this feature become available? While this is not really a bug, it might be a nice feature to have available. ------------------------------------------------------------------------ -- Edit this bug report at http://bugs.php.net/?id=14285&edit=1
