php-src/Zend/tests/bug43344_9.phpt

--TEST--
Bug #43344.9 (Wrong error message for undefined namespace constant)
--FILE--
<?php
namespace Foo;
function f($a=array(namespace\bar=>0)) {
    reset($a);
    return key($a);
}
echo f()."\n";
?>
--EXPECTF--
Fatal error: Uncaught Error: Undefined constant "Foo\bar" in %s:%d
Stack trace:
#0 %s(%d): Foo\f()
#1 {main}
  thrown in %sbug43344_9.php on line %d
Fixed bug #43344 (Wrong error message for undefined namespace constant) 2007-12-07 17:12:22 +00:00			`--TEST--`
			`Bug #43344.9 (Wrong error message for undefined namespace constant)`
			`--FILE--`
			`<?php`
			`namespace Foo;`
MF5: Merge namespaces changes 2008-12-04 20:12:30 +00:00			`function f($a=array(namespace\bar=>0)) {`
Reindent phpt files 2020-02-03 21:52:20 +00:00			`reset($a);`
			`return key($a);`
Fixed bug #43344 (Wrong error message for undefined namespace constant) 2007-12-07 17:12:22 +00:00			`}`
			`echo f()."\n";`
			`?>`
			`--EXPECTF--`
Review the usage of apostrophes in error messages Closes GH-5590 2020-05-26 12:10:57 +00:00			`Fatal error: Uncaught Error: Undefined constant "Foo\bar" 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): Foo\f()`
			`#1 {main}`
			`thrown in %sbug43344_9.php on line %d`