php-src/Zend/tests/objects_017.phpt

--TEST--
Testing visibility of object returned by function
--FILE--
<?php

class foo {
	private $test = 1;
}

function test() {
	return new foo;
}

test()->test = 2;

?>
--EXPECTF--
Fatal error: Uncaught Error: Cannot access private property foo::$test in %s:%d
Stack trace:
#0 {main}
  thrown in %s on line %d
New tests 2008-03-11 23:21:38 +08:00			`--TEST--`
			`Testing visibility of object returned by function`
			`--FILE--`
			`<?php`

			`class foo {`
			`private $test = 1;`
			`}`

			`function test() {`
			`return new foo;`
			`}`

			`test()->test = 2;`

			`?>`
			`--EXPECTF--`
Update exception names in tests after formatting changes. 2015-05-18 06:31:43 +08:00			`Fatal error: Uncaught Error: Cannot access private property foo::$test 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`