php-src/Zend/tests/ns_038.phpt

--TEST--
038: Name ambiguity (namespace name or internal class name)
--FILE--
<?php
namespace Exception;
function foo() {
  echo "ok\n";
}
\Exception\foo();
\Exception::bar();
?>
--EXPECTF--
ok

Fatal error: Uncaught Error: Call to undefined method Exception::bar() in %s:%d
Stack trace:
#0 {main}
  thrown in %sns_038.php on line 7
Fixed namespace name and internal class name ambiguity 2007-08-01 11:44:25 +00:00			`--TEST--`
			`038: Name ambiguity (namespace name or internal class name)`
			`--FILE--`
			`<?php`
			`namespace Exception;`
			`function foo() {`
			`echo "ok\n";`
			`}`
MF5: Merge namespaces changes 2008-12-04 20:12:30 +00:00			`\Exception\foo();`
			`\Exception::bar();`
Add many missing closing PHP tags to tests Closes GH-5958 2020-08-09 09:06:57 +00:00			`?>`
Fixed namespace name and internal class name ambiguity 2007-08-01 11:44:25 +00:00			`--EXPECTF--`
			`ok`

Review the usage of apostrophes in error messages Closes GH-5590 2020-05-26 12:10:57 +00:00			`Fatal error: Uncaught Error: Call to undefined method Exception::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 {main}`
			`thrown in %sns_038.php on line 7`