Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:81483 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 19937 invoked from network); 31 Jan 2015 12:44:13 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 31 Jan 2015 12:44:13 -0000 Authentication-Results: pb1.pair.com smtp.mail=pierre.php@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=pierre.php@gmail.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.192.46 as permitted sender) X-PHP-List-Original-Sender: pierre.php@gmail.com X-Host-Fingerprint: 209.85.192.46 mail-qg0-f46.google.com Received: from [209.85.192.46] ([209.85.192.46:56343] helo=mail-qg0-f46.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id A5/60-16633-C1ECCC45 for ; Sat, 31 Jan 2015 07:44:12 -0500 Received: by mail-qg0-f46.google.com with SMTP id i50so41733566qgf.5 for ; Sat, 31 Jan 2015 04:44:09 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=9w1fa7fkn7m34PFwXwScoGkOuy8rDp440CUEi6BZggQ=; b=pOzseCDRAtaG3XH74AWojcRW3jgwEvnEipB68RauQJt9L9htT9Ec0wVQIPfinQlEmL 4zk3GaGtDsHLd2E73OOFGW0W2L/tlmoFfxS6AAWHM4W2hTOBVwBsxSVdTqugMAdzJX4b HZSr+pWHouPAAqs4TuGlZBuI/Y7U4tj5im0sFHie4/hRTEdxIpS29/KuZ5CHjHPZXZ0w u0MUrHWrHxu+JMdvgY9cBW/7wl1BSn5yai/1D9FTTS8wOFdn99LE6s/Qr1pZZKix/9l/ hDSDfHbG/7TAqXT2TTOObWY2lscHljLgiGEWBqNAoJkGKJE7ucA2s+mJkWN6ucfvzz9R XnPA== MIME-Version: 1.0 X-Received: by 10.140.95.179 with SMTP id i48mr21085153qge.4.1422708249801; Sat, 31 Jan 2015 04:44:09 -0800 (PST) Received: by 10.96.3.168 with HTTP; Sat, 31 Jan 2015 04:44:09 -0800 (PST) Received: by 10.96.3.168 with HTTP; Sat, 31 Jan 2015 04:44:09 -0800 (PST) In-Reply-To: References: <54C8D36E.7010803@php.net> <39.52.31101.2585BC45@pb1.pair.com> Date: Sat, 31 Jan 2015 19:44:09 +0700 Message-ID: To: Tony Marston Cc: PHP internals Content-Type: multipart/alternative; boundary=001a11c16dfcd95d98050df213dd Subject: Re: [PHP-DEV] [RFC] [VOTE] pecl_http From: pierre.php@gmail.com (Pierre Joye) --001a11c16dfcd95d98050df213dd Content-Type: text/plain; charset=UTF-8 On Jan 31, 2015 5:57 PM, "Tony Marston" wrote: > > "Yasuo Ohgaki" wrote in message news:CAGa2bXZGLjrp6i2VDnkdgA8Dw7NothC9iE17tsT40kpbbhA9FA@mail.gmail.com... >> >> >> Hi Tony, >> >> On Fri, Jan 30, 2015 at 7:08 PM, Tony Marston >> wrote: >> >>> ""Pavel Kouril"" wrote in message >>> news:CAB6YZuzyMBAa5i3f9NsvebG2B7YJvO4RyVpy-eac78rsOJxdhQ@mail.gmail.com. .. >>> >>>> >>>> On Wed, Jan 28, 2015 at 1:17 PM, Michael Wallner wrote: >>>> >>> > >>> >>> Hello, >>>> >>>> >>>> just one observation - would be the name of the classes and namespaces >>>> stay the same after merging? I personally find the lowercased >>>> namespace name kinda weird, given that most of code written in PHP >>>> I've seen is using CamelCase. >>>> >>> >>> Just because that most of the code YOU have seen uses CamelCase does not >>> mean that CamelCase is the "standard". I programmed in other languages for >>> over 20 years before I switched to PHP, and in those languages the standard >>> was snake_case. That is the standard I still use, and I will object most >>> strongly to the notion that I should change the habits of a lifetime just to >>> suit the personal preferences of a junior programmer. By "junior" I mean >>> "years of experience", not "job title". >>> >> >> We have coding standard. >> >> From the CODING_STANDARDS in source. >> >> 6. Method names follow the 'studlyCaps' (also referred to as 'bumpy case' >> or 'camel caps') naming convention > > > > > > >> 7. Classes should be given descriptive names. Avoid using abbreviations >> where possible. Each word in the class name should start with a capital >> letter, without underscore delimiters (CamelCaps starting with a capital >> letter). The class name should be prefixed with the name of the 'parent >> set' (e.g. the name of the extension):: >> > <> > > If you are talking about coding standards which apply to PHP core then that is one thing, but trying to enforce those standards in userland code would be completely unacceptable. > > This is a discussion about adding features to core. They have to follow our CS. Period. There is nothing to discuss here. Sorry to sound harsh but this is going far OT. I would prefer to focus on the features and implementation details instead of that. --001a11c16dfcd95d98050df213dd--