2022年6月20日(月) 23:37 Lynn <kja...@gmail.com>: > On Mon, Jun 20, 2022 at 3:15 PM Guilliam Xavier <guilliam.xav...@gmail.com > > > wrote: > > > Hi, > > > > > https://wiki.php.net/rfc/random_extension_improvement > > > > Thanks, but I am not sure about your argument in "Classnames are not > > canonicalized": does "PHP applies strict PascalCase to class names" > > (which remains to be proved) really imply to rename *acronyms* (e.g. > > "CombinedLCG" to "CombinedLcg")? especially given existing classes > > like "SimpleXMLElement" (not "SimpleXmlElement"), and that the > > accepted "Class Naming" RFC (https://wiki.php.net/rfc/class-naming) > > voted for "PascalCase except Acronyms" (not "Always PascalCase") -- > > excerpts: > > > > Not specifically directed at this discussion, but perhaps this needs a > revision. HTTPStatus is much harder to read for me than HttpStatus and it's > unclear where the boundary of an acronym starts or stops. If anyone ever > decides to make an RFC for this, you have my vote. These Acronyms are > treated as words and thus should follow the same naming convention. If they > shouldn't be treated as words, write their full name: > HypertextTransferProtocolStatus. >
I support "PascalCase except Acronyms" for readability, but would like to see this clarified as I get very lost when implementing new features. I think it is necessary because I expect various OO APIs will be added in the future, like cURL. But, I do not have the right to vote. :)
