MR> $level = value($_POST['level'], NULL, INT);
MR> switch($level){
MR> case 0:
MR> echo "Welcome to level 0";
MR> break;
MR> case 1:
MR> echo "Welcome to level 1";
MR> break;
MR> case 2:
MR> echo "Welcome to level 2";
MR> break;
MR> default:
MR> echo "That level is invalid. Aborting"; /* $level == null or $level
>> 2 */
MR> }
This does not in any way call for a cast exception, it can easily be
rewritten as:
$level = (integer) value($_POST['level'], -1);
switch($level){
case 0:
echo "Welcome to level 0";
break;
case 1:
echo "Welcome to level 1";
break;
case 2:
echo "Welcome to level 2";
break;
default:
echo "That level is invalid. Aborting"; /* $level == -1 or
$level > 2
}
Don't get me wrong, an third parameter that specified a cast would not
hurt (in the way I see it being mainly used):
$x = (int) value($_GET['x'], 0);
$x = value($_GET['x'], 0, INT);
Not much different. I'm just saying that it should not be added if
the same thing can be accomplished with the same effort with existing
syntax. If a *frequent* use can be demonstrated for it, then I'd be
all for it.
Just my thoughts, thanks for reading.
--
Best regards,
Jason mailto:[EMAIL PROTECTED]
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
