php-src/tests/classes/static_properties_undeclared_read.phpt

--TEST--
Reading a non-existent static property
--FILE--
<?php
Class C {}
echo C::$p;
?>
--EXPECTF--
Fatal error: Uncaught Error: Access to undeclared static property C::$p in %s:%d
Stack trace:
#0 {main}
  thrown in %s on line 3
Additional class related tests. 2009-06-17 10:38:24 +00:00			`--TEST--`
			`Reading a non-existent static property`
			`--FILE--`
			`<?php`
			`Class C {}`
			`echo C::$p;`
			`?>`
			`--EXPECTF--`
Review the usage of apostrophes in error messages Closes GH-5590 2020-05-26 12:10:57 +00:00			`Fatal error: Uncaught Error: Access to undeclared static property C::$p 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 3`