php-src/Zend/tests/dynamic_call_003.phpt

--TEST--
Testing dynamic call with invalid method name
--FILE--
<?php 

$a = new stdClass;
$b = 1;

$a::$b();

?>
--EXPECTF--
Fatal error: Uncaught exception 'EngineException' with message 'Function name must be a string' in %s:%d
Stack trace:
#0 {main}
  thrown in %s on line %d
- New tests 2008-05-11 03:15:13 +00:00			`--TEST--`
			`Testing dynamic call with invalid method name`
			`--FILE--`
			`<?php`

			`$a = new stdClass;`
			`$b = 1;`

			`$a::$b();`

			`?>`
			`--EXPECTF--`
Display EngineExceptions like ordinary exceptions TypeException stays as-is for now because it uses messages that are incompatible with the way exception messages are displayed. closure_038.phpt and a few others now show that we're generating too many exceptions for compound operations on undefined properties -- this needs to be fixed in a followup. 2015-05-15 19:04:07 +00:00			`Fatal error: Uncaught exception 'EngineException' with message 'Function name must be a string' in %s:%d`
			`Stack trace:`
			`#0 {main}`
			`thrown in %s on line %d`