php-src/Zend/tests/isset_expr_error.phpt

--TEST--
Error message for isset(func())
--FILE--
<?php
isset(1 + 1);
?>
--EXPECTF--
Fatal error: Cannot use isset() on the result of an expression (you can use "null !== expression" instead) in %s on line %d
Allow arbitrary expressions for empty() This change is as per RFC https://wiki.php.net/rfc/empty_isset_exprs. The change allows passing the result of function calls and other expressions to the empty() language construct. This is accomplished by simply rewriting empty(expr) to !expr. The change does not affect the suppression of errors when using empty() on variables. empty($undefinedVar) will continue not to throw errors. When an expression is used inside empty() on the other hand, errors will not be suppressed. Thus empty($undefinedVar + $somethingElse) will throw a notice. The change also does not make empty() into a real function, so using 'empty' as a callback is still not possible. In addition to the empty() changes the commit adds nicer error messages when isset() is used on function call results or other expressions. 2012-04-12 09:54:52 +00:00			`--TEST--`
			`Error message for isset(func())`
			`--FILE--`
			`<?php`
			`isset(1 + 1);`
			`?>`
			`--EXPECTF--`
			`Fatal error: Cannot use isset() on the result of an expression (you can use "null !== expression" instead) in %s on line %d`