Mixed case seems easier, especially when you have two acronyms next to each other. Case in point: Zend_Controller_Request_Http::isXmlHttpRequest().
Is this formatted in acronym case? Then it should be isXMLHTTPRequest(). Is this formatted according to its actual formatting in JavaScript? Then it should be isXMLHttpRequest() (see http://www.w3.org/TR/XMLHttpRequest/). Sure, PHP is case insensitive with regard to method names, but Zend_XmlRpc would be Zend\XMLRPC, wouldn't it? Seems awkward. -Matt On Fri, Jul 9, 2010 at 1:07 PM, Matthew Weier O'Phinney <matt...@zend.com>wrote: > 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: > > http://short.ie/zf-acrocase > > 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! > > -- > Matthew Weier O'Phinney > Project Lead | matt...@zend.com > Zend Framework | http://framework.zend.com/ > PGP key: http://framework.zend.com/zf-matthew-pgp-key.asc >
