php-src/Zend/tests/dynamic_call_002.phpt

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

$a = new stdClass;

$a::$a();

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

			`$a = new stdClass;`

			`$a::$a();`

			`?>`
			`--EXPECTF--`
Update exception names in tests after formatting changes. 2015-05-18 06:31:43 +08:00			`Fatal error: Uncaught Error: Function name must be a string in %s:%d`
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-16 03:04:07 +08:00			`Stack trace:`
			`#0 {main}`
			`thrown in %s on line %d`