php-src/Zend/tests/errmsg_044.phpt

--TEST--
Trying use object of type stdClass as array
--FILE--
<?php

$a[0] = new stdclass;
$a[0][0] = new stdclass;

?>
--EXPECTF--
Fatal error: Uncaught Error: Cannot use object of type stdClass as array in %s:%d
Stack trace:
#0 {main}
  thrown in %s on line %d
New tests 2008-03-12 13:01:59 +00:00			`--TEST--`
			`Trying use object of type stdClass as array`
			`--FILE--`
			`<?php`

			`$a[0] = new stdclass;`
			`$a[0][0] = new stdclass;`

			`?>`
Fixed test 2008-03-12 15:20:41 +00:00			`--EXPECTF--`
Update exception names in tests after formatting changes. 2015-05-17 22:31:43 +00:00			`Fatal error: Uncaught Error: Cannot use object of type stdClass as array 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`