Clarify abbreviations and acronyms in PSR-1 method names. #48
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.
Warning: Given the wide-spread adoption of strict camelCase in user-space PHP code, I realize and naturally expect some push-back here.
However. PHP core is crystal clear with regard to acronyms and abbreviations, at least in its more "recent" extensions.
Thus, if PSR-* has any goal of consistency, then it should definitely follow the lead of the very language interpreter it is trying to form standards for. Otherwise, it would intentionally be inconsistent with class methods provided by PHP core.
Two possible options:
Diverge from PHP core and "do what others do."
Essentially introducing and enforcing a huge inconsistency between user space method names and PHP core method names.
Do what PHP core does. Native consistency.
Background: http://drupal.org/node/1627350