Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:99319 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 78683 invoked from network); 2 Jun 2017 13:01:38 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 2 Jun 2017 13:01:38 -0000 Authentication-Results: pb1.pair.com smtp.mail=rowan.collins@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=rowan.collins@gmail.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.52 as permitted sender) X-PHP-List-Original-Sender: rowan.collins@gmail.com X-Host-Fingerprint: 74.125.82.52 mail-wm0-f52.google.com Received: from [74.125.82.52] ([74.125.82.52:38665] helo=mail-wm0-f52.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 9F/26-12681-0B161395 for ; Fri, 02 Jun 2017 09:01:37 -0400 Received: by mail-wm0-f52.google.com with SMTP id n195so26422492wmg.1 for ; Fri, 02 Jun 2017 06:01:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:user-agent:in-reply-to:references:mime-version :content-transfer-encoding:subject:to:from:message-id; bh=II0WS4Ie8Apaw+S2qxsBVDmZpSW40Y5RMuTINnxwN5A=; b=VlHCLRwtB8PPD4OULre5v+QeMCFU2RPx9jFK4cOCsBzmmw9wfp8UgzsvccYOloxyWE Wo+vGvzzV7t9r/raseV6HnB0viO90v7cqAjtb0+paGEppbtCBL8uuuP/mAZ5oT9XigaU 8eNW0Ld17un1QKUQTSZ5FR8fRMSvCmdFvcfJXyFNuyHeuvogLIQtFRWFbWxVmum+7VEL iIu+AdYVgYOOd6LZ8ydGC+RwRPYzAb4QKm5+ZlhYQDHShHvPrZFYGVe8t3Is3UUN4wFz ggy2l4QEwIuQcayxMKS2Q08Ix2MtXt9VLB5L8rNG1CInpgq1XJ+rl4JP48ySO3PRKi1P n6Zg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:user-agent:in-reply-to:references :mime-version:content-transfer-encoding:subject:to:from:message-id; bh=II0WS4Ie8Apaw+S2qxsBVDmZpSW40Y5RMuTINnxwN5A=; b=qPZ7DsEV3gSFJ92rwZsGZAGCYql3BYpubyQakD0qU4/RsnWIt/r5jtzl2YjQjo9Cu3 gmyUEti4TcO5QPd5VLs/bFuEksHLvcm0GHI08CGbZfQ+6PvEiVWp+tJ0GfZUfT7jBQUb i5IBr3Q6rgoMTCFRS0vpeaKVIHhT7Ym8xsdTuBwKiJBdd418KldNS+GrfK6b871hX9O3 xJaUes5e+4OLhT/kg0ay8+VLqZ0idQGTbhteLf08ZbXETjD69ts5r70sEtNgsNXrKymv 002oEdJe9ZLaToBflgjSdbT9AJkvogWO9hnx39CNBG6OnTElNuLiIv4XplLLsonVjTtd OEuQ== X-Gm-Message-State: AODbwcDnrPp8bNx65QCecjrFfhor/cvSlqixh6xYZr8hIOw+LM5qkCLr GJ1tXN1n9ilJyu01SXA= X-Received: by 10.28.54.40 with SMTP id d40mr3238871wma.70.1496408492728; Fri, 02 Jun 2017 06:01:32 -0700 (PDT) Received: from [10.7.17.11] (188.29.165.251.threembb.co.uk. [188.29.165.251]) by smtp.gmail.com with ESMTPSA id o97sm23901419wrc.48.2017.06.02.06.01.31 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 02 Jun 2017 06:01:31 -0700 (PDT) Date: Fri, 02 Jun 2017 14:01:30 +0100 User-Agent: K-9 Mail for Android In-Reply-To: References: <9dffe898-e550-c6d6-46bd-86dcf74735ea@fleshgrinder.com> <9652e487-86e7-20b7-ca1f-bd28a94f514b@gmail.com> <86dba466-a764-522b-6990-39fd7668a79c@fleshgrinder.com> <51.72.43873.46BDF295@pb1.pair.com> <41F2B884-5DB7-4691-B540-97B0DAEAAFF5@gmail.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----5PJL3OJKF86F0XJCAQBHD92W2HK4WR" Content-Transfer-Encoding: 7bit To: internals@lists.php.net Message-ID: <1C2E36C5-BC15-493B-BBBA-9ABD7CF82B18@gmail.com> Subject: Re: [PHP-DEV] Class Naming in Core From: rowan.collins@gmail.com (Rowan Collins) ------5PJL3OJKF86F0XJCAQBHD92W2HK4WR Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On 2 June 2017 08:56:57 BST, Tony Marston wrote= : > Different groups of people follow different naming conventions simply=20 > because there is no universally accepted standard=2E The phrase here is "groups of people"; the PHP Internals team is such a gr= oup, and it is perfectly reasonable for that group to follow a naming conve= ntion=2E > All you will do is annoy those people who are forced to >change,=20 >especially when it means taking a name in a readable format and >changing it=20 >to a less-readable format=2E Let's just be clear here: you are not being asked to change a single line = of your PHP code=2E If, at some stage, you want to write a PHP extension, in C, which introduc= es new classes, AND you want that extension to be distributed and maintaine= d as part of the official distribution of PHP, then you can read the naming= conventions once, write your class names in the format it suggests, and al= l will be fine=2E If you never do this, the existence of a convention will make absolutely n= o difference to you, apart from the benefits, however small, that consisten= cy brings=2E Regards, --=20 Rowan Collins [IMSoP] ------5PJL3OJKF86F0XJCAQBHD92W2HK4WR--