Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:99292 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 24734 invoked from network); 31 May 2017 09:26:14 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 31 May 2017 09:26:14 -0000 X-Host-Fingerprint: 62.31.75.76 76.75-31-62.static.virginmediabusiness.co.uk Received: from [62.31.75.76] ([62.31.75.76:2031] helo=localhost.localdomain) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id B2/EA-43873-53C8E295 for ; Wed, 31 May 2017 05:26:14 -0400 Message-ID: To: internals@lists.php.net References: <9dffe898-e550-c6d6-46bd-86dcf74735ea@fleshgrinder.com> <9652e487-86e7-20b7-ca1f-bd28a94f514b@gmail.com> <86dba466-a764-522b-6990-39fd7668a79c@fleshgrinder.com> In-Reply-To: <86dba466-a764-522b-6990-39fd7668a79c@fleshgrinder.com> Date: Wed, 31 May 2017 10:26:06 +0100 Lines: 2 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="utf-8"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal Importance: Normal X-Newsreader: Microsoft Windows Live Mail 16.4.3564.1216 X-MimeOLE: Produced By Microsoft MimeOLE V16.4.3564.1216 X-Posted-By: 62.31.75.76 Subject: Re: [PHP-DEV] Class Naming in Core From: TonyMarston@hotmail.com ("Tony Marston") wrote in message news:86dba466-a764-522b-6990-39fd7668a79c@fleshgrinder.com... > >Hey Stas! > >On 5/30/2017 1:00 AM, Stanislav Malyshev wrote: >> Hi! >> >>> People are complaining over at Reddit [1] >> >> Isn't it what Reddit is for? ;) >> > >I guess it is. ;) > >>> I know that this is probably a topic nobody cares much about, at least >>> we did not end up in this kind of bikeshedding in the UUID discussion >>> thread, but it is after all an important question when designing a >>> language. >> >> I personally don't think it is a very important decision, since nothing >> much would change either way, but my preference would be: >> >> 1. If there's an established acronym, keep it (GMP, DOM, XML, HTTP). >> 2. If it's just words, use CamelCase. >> >> Second preference is all CamelCase, treating acronyms as a single word >> (e.g. RpcOverHttpsViaXml). >> > >Exactly how I see it. I am only asking to decide on one of both and put >it into our coding standard so people who keep on complaining can be >pointed there, and we're done. > I should point out that snake_case was the universal standard decades before some people switched to CamelCase. That was only because some software could not handle long names, but could handle both upper and lower case, so an upper case character was used instead of an underscore. That limitation of the size of names no longer exists in any modern software, so the continued use of CamelCase is out of habit and not necessity. -- Tony Marston