Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:99333 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 36486 invoked from network); 3 Jun 2017 08:22:19 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 3 Jun 2017 08:22:19 -0000 Authentication-Results: pb1.pair.com header.from=lists@rhsoft.net; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=lists@rhsoft.net; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain rhsoft.net designates 91.118.73.15 as permitted sender) X-PHP-List-Original-Sender: lists@rhsoft.net X-Host-Fingerprint: 91.118.73.15 mail.thelounge.net Received: from [91.118.73.15] ([91.118.73.15:15819] helo=mail.thelounge.net) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 28/AC-12681-9B172395 for ; Sat, 03 Jun 2017 04:22:18 -0400 Received: from srv-rhsoft.rhsoft.net (Authenticated sender: h.reindl@thelounge.net) by mail.thelounge.net (THELOUNGE MTA) with ESMTPSA id 3wfvFd6hG7zXMn for ; Sat, 3 Jun 2017 10:22:13 +0200 (CEST) To: internals@lists.php.net References: <9dffe898-e550-c6d6-46bd-86dcf74735ea@fleshgrinder.com> Message-ID: <2e71e158-0fbc-6880-3893-597c2be9bac4@rhsoft.net> Date: Sat, 3 Jun 2017 10:22:13 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.1.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: de-CH Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] Class Naming in Core From: lists@rhsoft.net ("lists@rhsoft.net") Am 03.06.2017 um 10:10 schrieb Tony Marston: > "Dan Ackroyd" wrote in message > news:CA+kxMuRoMvy6vB0YKd6Ejqu8AsKxrO2x6F9y5i9+cxfJSJ-ihg@mail.gmail.com... >> >> On 29 May 2017 at 23:13, Fleshgrinder wrote: >>> Hey guys! >>> >>> People are complaining over at Reddit [1] >> >> While the "STD" is slightly humorous, it is unneeded verbosity, and >> will lead to pointless arguments in the future of whether other >> features in the future should catch the STD name, or whether they >> should be directly under PHP. I would recommend not using it. >> >> I don't care about case, though there may be a slight argument that >> upper-casing initialisations is the 'standard' in PHP core. > > It can only be the "standard" if it has been documented as such and > everyone follows it. If it was not documented as such from the start of > the project then it does not qualify. It may have become the most > commonly used in a selection of alternatives, but that does not give > anyone the right to now say that it has become the standard and should > be enforced. That strikes me as being dictatorial and authoritarian, as > well as requiring large amounts of effort without offering any tangible > benefits. I'm "consistency" is not a valid benefit in my book that's fine for your personal book, everywhere else consistency belongs to code quality