php-src/Zend/tests/bug52484_3.phpt

--TEST--
Bug #52484.3 (__set() ignores setting properties with empty names)
--FILE--
<?php

class A {	
	function __get($prop) {
		var_dump($this->$prop);
	}
}

$a = new A();
$prop = null;

var_dump($a->$prop);

?>
--EXPECTF--
Fatal error: Uncaught Error: Cannot access empty property in %s:%d
Stack trace:
#0 %s(%d): A->__get('')
#1 {main}
  thrown in %s on line %d
- Fixed bug #52484 (__set() ignores setting properties with empty names) 2010-08-01 13:27:02 +00:00			`--TEST--`
			`Bug #52484.3 (__set() ignores setting properties with empty names)`
			`--FILE--`
			`<?php`

			`class A {`
			`function __get($prop) {`
			`var_dump($this->$prop);`
			`}`
			`}`

			`$a = new A();`
			`$prop = null;`

			`var_dump($a->$prop);`

			`?>`
			`--EXPECTF--`
Update exception names in tests after formatting changes. 2015-05-17 22:31:43 +00:00			`Fatal error: Uncaught Error: Cannot access empty property 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 %s(%d): A->__get('')`
			`#1 {main}`
			`thrown in %s on line %d`