|  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Doc Bug #77948 Wrong Namespaces FAQ item interpretation/explanation
Submitted: 2019-04-28 08:32 UTC Modified: 2019-04-28 08:39 UTC
From: dn dot permyakov at gmail dot com Assigned:
Status: Open Package: Documentation problem
PHP Version: 7.1.28 OS: MacOS Mojave
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: dn dot permyakov at gmail dot com
New email:
PHP Version: OS:


 [2019-04-28 08:32 UTC] dn dot permyakov at gmail dot com
From manual page:

There is a list item:
 "Import names cannot conflict with classes defined in the same file".

Given example shows that class defined NOT in the SAME file but in the file that included into main file together with second one. 

This changes the sense of the phrase completely. Cause it CAN and WILL conflict with classed defined in the SAME file(try to move MyClass into file2.php and you'll see)

The description should be something like "Import names cannot conflict with each other" or something like that.


Add a Patch

Pull Requests

Add a Pull Request


AllCommentsChangesGit/SVN commitsRelated reports
 [2019-04-28 08:39 UTC] dn dot permyakov at gmail dot com
Better description version would be "Import names cannot conflict with aliases existing in the same file"
 [2019-08-25 19:46 UTC] dominic dot mayers at meditationstudies dot org
Here, "cannot" means "are not allowed to". The item says "Import names are not allowed to conflict with classes defined in the same file." Is this clearer?
PHP Copyright © 2001-2020 The PHP Group
All rights reserved.
Last updated: Fri Jul 03 16:01:29 2020 UTC