One complaint we've heard often of ZF users is confusion over how acronyms are represented in class names.
As an example, many suggest that "Zend_PDF" is more semantically correct and easier to remember than "Zend_Pdf". On the other side of the coin, many developers feel that our MixedCasing or Titlecasing of acronyms is a simple, easily learned rule that makes typing easier.
For ZF2, we started converting code to use each acronym's proper casing. However, we're not done yet, and there are good arguments on both sides of the debate.
Our team is at a point where we actually think the important thing is to simply have a rule. As such, we're leaving it up to you, our users, to decide.
Simply fill out this form:
We'll close it in a week or so, and use the decision from that form to determine how to proceed. We even promise to publically export the results, in the interest of transparency. :)
So, help choose the direction of ZF2 today!
Comments (Login to leave comments)
One comment though: make sure that ZF can work with this as well. In some places (I don't remember where exactly, but I think I encountered this in app resource class names) it converts everything to lowercase (except first character) to create the class name and try to load it. If you have a mixed case class, it will not be able to find it.
Throughout the years working with this zf-convention convinced me that mixedCasing leads to less confusion and is easier to type. The rule is equally easy to remember and easier to apply.
So this should be no question. We will stay with mixed case.
Keep it as MixedCase. Then you don't have to think about whether it refers to an acronym or not. Haven't seen one vote for ACRONYM here, so maybe that says something...
MixedCase!