Output an E_STRICT error on class/function case mismatch #965
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
flaupretre
force-pushed
the
detect-case-mismatch
branch
2 times, most recently
from
7c14e9d to
1d9cc25
Compare
flaupretre
force-pushed
the
detect-case-mismatch
branch
from
1d9cc25 to
3bb3bcf
Compare
|
Closing as per the last ML discussion on this topic this won't be further pursued in the near future. For reference, here's the thread: http://markmail.org/message/kupyh4g5dnjujo66 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Raises an E_STRICT error when a function or a class is referenced using a name which is not exactly the name that was used in the class/function declaration.
This is a first step towards deprecating case-insensitive matches for functions and classes (and namespaces, of course).
Note: This is just a prototype. It does not match every cases yet.