Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:110296 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 97336 invoked from network); 28 May 2020 20:12:49 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 28 May 2020 20:12:49 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id E99991804D3 for ; Thu, 28 May 2020 11:53:34 -0700 (PDT) X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on php-smtp4.php.net X-Spam-Level: X-Spam-Status: No, score=-0.7 required=5.0 tests=BAYES_05,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_NONE, RCVD_IN_MSPIKE_H2,SPF_HELO_NONE,SPF_NONE autolearn=no autolearn_force=no version=3.4.2 X-Spam-ASN: AS15169 209.85.128.0/17 X-Spam-Virus: No X-Envelope-From: Received: from mail-qv1-f48.google.com (mail-qv1-f48.google.com [209.85.219.48]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by php-smtp4.php.net (Postfix) with ESMTPS for ; Thu, 28 May 2020 11:53:34 -0700 (PDT) Received: by mail-qv1-f48.google.com with SMTP id dp10so1853572qvb.10 for ; Thu, 28 May 2020 11:53:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=benramsey.com; s=google; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=RQQdSpybqmhHtNTSSrZHiD3m1PZnHCwU0l4hmWH0XNA=; b=h2fJkrpQr1XRA+itYWof3fVAvc3/DTO0fjPDE49PJNS2lpefLgCGFP+M0eB0SW3E4L 3oKDla6dJxjshJhhWteXu65HQVjHsHjG95FieI7GAYN49sxH5nRz2oYvfwFEzXgzLLxl 6c79HUoN+MxVjd/hz6hHk/7etPWyczrJTFDjvsnudmDCq4ALs3FuS3H0koSvEfpZIMc/ 9CymdH9fG+qgx2BH6G0cKnzfAYWjWbtF6hB7TQVXBkrn/OaBC8PY0hNq3j/6cJpo8BDt cBNnom0OHkTQ6TK70CnND8Ni1rO1Bgg76/wfTP10fctQRynvgxsNiPMuIXiTzoCPe+dW 7Cgw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=RQQdSpybqmhHtNTSSrZHiD3m1PZnHCwU0l4hmWH0XNA=; b=iTuzs0ojFrGPNB/9s68FGGPk+v3NnevgDwRy1qGUydViz0rAe/DSdgfObGXi98AD7r Yi63YYYA4Ez4+zUE5CVimfCYpdSl8uZO3hxJhhA3spdSUC1wi4AWNOjCvK1mbFM4TWnw MEC+SvS2aLkPY6ulfB4sivb3kv35w52razq9UJP6PZFXz6hokAIrcjl3LUaV3AVrxcfi MjpJMRkaMgtfOQZqiswQ7oBe7EHAtGeofhANNseArHmkUqSGvqHGB9bA2WJ5SPtpx24E tBfKSODToFfT6L46xDAIn2lM3Hnbxefy+6TUkiTDruZMcxtdtOr7cRapid4ZRUnUmYrA vl+g== X-Gm-Message-State: AOAM5307kADtm2h7kn1ynGHfPqXMlLPfzcZII2pEntCrKNCCg3lDqs1x 4vBaP4btzHkGLtzytG+W3Vqv+w== X-Google-Smtp-Source: ABdhPJwOBXfa3vGRb2tQk7iBGEZWcTmNNiooeWy4TYCBLdW24/HBlvIe4+rI7CFs6z1PrxA4sgjbQQ== X-Received: by 2002:a0c:8426:: with SMTP id l35mr4586869qva.223.1590692011053; Thu, 28 May 2020 11:53:31 -0700 (PDT) Received: from [10.10.42.56] (h96-61-170-50.lvrgtn.dsl.dynamic.tds.net. [96.61.170.50]) by smtp.gmail.com with ESMTPSA id u14sm5551226qtq.46.2020.05.28.11.53.29 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Thu, 28 May 2020 11:53:30 -0700 (PDT) Message-ID: Content-Type: multipart/signed; boundary="Apple-Mail=_F17C42D6-7E9C-4F78-9E65-33A01AE89605"; protocol="application/pgp-signature"; micalg=pgp-sha256 Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.80.23.2.2\)) Date: Thu, 28 May 2020 13:53:27 -0500 In-Reply-To: Cc: PHP Internals List To: =?utf-8?Q?Micha=C5=82_Brzuchalski?= References: X-Mailer: Apple Mail (2.3608.80.23.2.2) Subject: Re: [PHP-DEV] [RFC][VOTE] PHP Namespace in core From: ben@benramsey.com (Ben Ramsey) --Apple-Mail=_F17C42D6-7E9C-4F78-9E65-33A01AE89605 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 > On May 22, 2020, at 01:14, Micha=C5=82 Brzuchalski = wrote: >=20 > Hi Internals, >=20 > We have just opened the vote on the PHP namespace in core RFC. The = voting > will be open for two weeks, until 2020-06-05 06:00 UTC. >=20 > Link: https://wiki.php.net/rfc/php-namespace-in-core#vote In light of recent discussions on attribute naming schemes, I=E2=80=99m concerned that future RFC discussions will be riddled with noisy back-and-forth messages concerning what and how to name things. I=E2=80=99= m not passing any judgement on these types of conversations, since I agree that naming things is important, but I also think the use of a specialized namespace for core symbols is inevitable, and it=E2=80=99s = better to tackle this now than later. With that in mind, I=E2=80=99m changing my =E2=80=9Cno=E2=80=9D vote to = a =E2=80=9Cyes=E2=80=9D for this RFC. As a side note: one of the reasons I dislike the `\PHP` namespace is because I think it looks ugly. I don=E2=80=99t know why I have this = impression, and it=E2=80=99s probably the wrong reason to vote =E2=80=9Cno=E2=80=9D = on something, but it=E2=80=99s one of the factors that led me to vote =E2=80=9Cno.=E2=80=9D I=E2=80=99ll = probably standardize on capitalizing the namespace as `\Php` (I tend to follow the Microsoft .NET capitalization conventions [1]). Cheers, Ben [1]: = https://docs.microsoft.com/en-us/dotnet/standard/design-guidelines/capital= ization-conventions --Apple-Mail=_F17C42D6-7E9C-4F78-9E65-33A01AE89605 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP -----BEGIN PGP SIGNATURE----- iHUEAREIAB0WIQToXQMR3fpbrPOmEOewLZeYnIwHGwUCXtAIpwAKCRCwLZeYnIwH G5shAQCZRqVRku9E9VBy9buhk3Vcpst9GXoBCdljQq2jxcwj2AEAi/msHSHvzL4h IP/FOsmhStXF8FF28z7EKU95AfZDYUY= =VYw5 -----END PGP SIGNATURE----- --Apple-Mail=_F17C42D6-7E9C-4F78-9E65-33A01AE89605--