|  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Request #73049 Confusing namespace when calling missing function
Submitted: 2016-09-08 15:10 UTC Modified: 2016-09-08 16:57 UTC
Avg. Score:2.0 ± 1.0
Reproduced:1 of 2 (50.0%)
Same Version:0 (0.0%)
Same OS:0 (0.0%)
From: david at grudl dot com Assigned:
Status: Open Package: Scripting Engine problem
PHP Version: Irrelevant OS:
Private report: No CVE-ID: None
View Add Comment Developer Edit
Welcome! If you don't have a Git account, you can't do anything here.
You can add a comment by following this link or if you reported this bug, you can edit this bug over here.
Block user comment
Status: Assign to:
Bug Type:
From: david at grudl dot com
New email:
PHP Version: OS:


 [2016-09-08 15:10 UTC] david at grudl dot com
When you call undefined global function inside namespace, the error message contains namespace, which is usually confusing.

Example: Suppose that I have not enabled extension 'json' by mistake. Now this code


namespace Nette;

echo json_encode($x); 


leads to error "Call to undefined function Nette\json_encode()". The better message should be "Call to undefined function json_encode()".

I know how works function name resolution, but consider these points:

1) functions are used in namespaces only rarely
2) functions are usually called without leading slash, i.e. not fully qualified
3) both error messages are correct, none is more correct than the other

So it is much more likely that I call a global function, so it would be preferable to use message WITHOUT namespace.


Add a Patch

Pull Requests

Add a Pull Request


AllCommentsChangesGit/SVN commitsRelated reports
 [2016-09-08 16:57 UTC]
In my opinion the current error message is preferable over your
suggestion, because looking for a global function (or constant for
that matter) is only a *fallback*.
PHP Copyright © 2001-2021 The PHP Group
All rights reserved.
Last updated: Sat May 15 18:01:23 2021 UTC