Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 3.1.0-dev
-
Fix Version/s: 3.1.0-b1
-
Component/s: None
-
Labels:None
Description
The situation of having both a/b_foo.php and a/b/bar.php happens during refactoring when some of the classes have been moved under a/b and some not.
The current behavior is not user friendly - php says class is not found where it was found just fine in the previous version of the tree and the class has not changed.
Assuming we own phpbb_ namespace it may be ok to always try searching for a/b_foo.php. Otherwise maybe define a constant in test suite, if it is defined do the second loading pass and print a warning if any files are found there.
Activity
I think that would be fine. We can spam notices or somesuch in such cases.
(Printing a notice and not loading the file, that is.)
This should be addressed by the coding guidelines.
Namespaces 
This was intentionally not done to enforce a proper structuring of files. The autoloading RFC defines this quite clearly. I'm ok with searching for the other file and printing a warning in debug mode / during testing. But I don't want to alter the regular loading behaviour.