php-src/Zend/tests/indirect_call_array_001.phpt

--TEST--
Indirect method call by array - Invalid class name
--FILE--
<?php

$arr = array('a', 'b');
$arr();

?>
--EXPECTF--
Fatal error: Uncaught Error: Class "a" not found in %s:%d
Stack trace:
#0 {main}
  thrown in %s on line %d
- New tests for new feature 2011-06-14 02:05:37 +00:00			`--TEST--`
			`Indirect method call by array - Invalid class name`
			`--FILE--`
			`<?php`

			`$arr = array('a', 'b');`
			`$arr();`

			`?>`
			`--EXPECTF--`
Review the usage of apostrophes in error messages Closes GH-5590 2020-05-26 12:10:57 +00:00			`Fatal error: Uncaught Error: Class "a" not found 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-15 19:04:07 +00:00			`Stack trace:`
			`#0 {main}`
			`thrown in %s on line %d`