Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:99244
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.218.49 as permitted sender)
To: Fleshgrinder <php@fleshgrinder.com>,
 php-internals <internals@lists.php.net>
References: <9dffe898-e550-c6d6-46bd-86dcf74735ea@fleshgrinder.com>
Message-ID: <9652e487-86e7-20b7-ca1f-bd28a94f514b@gmail.com>
Date: Mon, 29 May 2017 16:00:29 -0700
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0)
 Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <9dffe898-e550-c6d6-46bd-86dcf74735ea@fleshgrinder.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Class Naming in Core
From: smalyshev@gmail.com (Stanislav Malyshev)

Hi!

> People are complaining over at Reddit [1]

Isn't it what Reddit is for? ;)

> 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).

-- 
Stas Malyshev
smalyshev@gmail.com