Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:110904 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 89114 invoked from network); 9 Jul 2020 19:09:26 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 9 Jul 2020 19:09:26 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 0FCF7180384 for ; Thu, 9 Jul 2020 11:00:40 -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=-2.1 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM,HTML_MESSAGE, RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H2,SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.2 X-Spam-Virus: No X-Envelope-From: Received: from mail-io1-f47.google.com (mail-io1-f47.google.com [209.85.166.47]) (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, 9 Jul 2020 11:00:39 -0700 (PDT) Received: by mail-io1-f47.google.com with SMTP id q8so3271601iow.7 for ; Thu, 09 Jul 2020 11:00:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=0/smXR+u3u5vYicOHezsZWONvzBiiv04A4qfi4rJmmQ=; b=Tg614s4P/Q8fSOsHwmDz6Sw8uYai2KZTFiOk/6yPIS5rV56o7kuNmqedzc28XFs79M sSxfLGo2uTuVqQw3Kv9pp9iIhTa7Ws0R6LQCL2V7PnhWf+nrcl6/Vr9C946WxKN+n6yE isx0+cEcbufPoJSIsmI1FmDZh3MskUwwXdoSGXDbwN3Qnz/yy33lsArwzTIUArJchqHH yZrHm/bfxqazzSk7Ax/sIDe/UB+xz+hy1lS2r0w0rLSNnMIwoXrBKINFz//EKLkycLmf 2SOGw5uuIKvRQQGUMOoYJLF1hxrLRR7V9xm/6CC61e36RetcI74AJZJjUhh5jn5J3mqv 6Gyw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=0/smXR+u3u5vYicOHezsZWONvzBiiv04A4qfi4rJmmQ=; b=OvOYTku2+8hMAfr0KGcQ0USD1ZnGU4xWHEN/+zU5kxv1KN8egQ8oRRgShxX/CMWarJ RCcsTDXkuxR3EIkHguV8cMre+GyFaxSopDeDCXelR8Kmf7MiAMQfCu0g6ZhA4Q+YCh7Q 6mQ9ac4VNDY3BqhFAliwCfq9iyWZgw9LoXVAk0V77sVl1V2y0OOIAboLqBK4YZ7iApi3 osoCJKhHIFtlkxw9NDbpuVd1o1uVyBPmOrOlIt+7T0ktlyDV2IcmHmfuQCGx9SFvWk6h OgtK03laFrgrLCV6eqNmRu4qSLhR7+Uh+4yHRpwHnhEobQ2kx/4nAa0CUWwYPIepRjMq g/Pw== X-Gm-Message-State: AOAM533P4IlOFhYQrCbSrXrf589SUBXJYHEdTZ/7edkeO2RFJLTI061B B3dL84Ywx90TE8+qGJYJN34F7WO5hQfQz5H+nodKJtNv X-Google-Smtp-Source: ABdhPJwS+Nxk35VmNwL9rMaWtoATcFBrpRGCSoE7R/RHbaM9bjNeyz+Rd9ho9y1N6GP6/NSnrYhTYP3lmMnhc1p8zuA= X-Received: by 2002:a05:6602:2103:: with SMTP id x3mr43460453iox.130.1594317636411; Thu, 09 Jul 2020 11:00:36 -0700 (PDT) MIME-Version: 1.0 References: <0771c3ac-53ec-4a7f-a4e9-6ae3c9b1f1f6@www.fastmail.com> <49fd7972-8cec-4207-99af-6c77c2328211@www.fastmail.com> In-Reply-To: Date: Thu, 9 Jul 2020 19:00:25 +0100 Message-ID: To: php internals Content-Type: multipart/alternative; boundary="00000000000060abd105aa060019" Subject: Re: [PHP-DEV] [RFC] \PHP namespace usage heuristics From: rowan.collins@gmail.com (Rowan Tommins) --00000000000060abd105aa060019 Content-Type: text/plain; charset="UTF-8" On Thu, 9 Jul 2020 at 18:14, Derick Rethans wrote: > On Thu, 9 Jul 2020, Rowan Tommins wrote: > > > And yet we have repeatedly had discussions about whether this or that > > feature should or shouldn't be prefixed with a namespace. If you think > > the correct answer to "when should we use the PHP\ prefix?" is > > "never", I urge you to put forward an RFC making that the policy. > > That is already the policy: > https://www.php.net/manual/en/userlandnaming.rules.php > > Specifically "PHP owns the top-level namespace but tries to find decent > descriptive names and avoid any obvious clashes" > That is not the same thing at all. That states that PHP may use the global namespace; it doesn't say it will never use any other namespace. And https://www.php.net/manual/en/language.namespaces.rationale.php says essentially the same thing about the PHP\* namespace: > The Namespace name *PHP*, and compound names starting with this name (like *PHP\Classes*) are reserved for internal language use and should not be used in the userspace code. At the very least, it is not universally accepted that the policy is never to use the PHP namespace, or we wouldn't keep having this conversation. So, again, if anyone thinks that the policy should be to never use the PHP\ namespace prefix, please put it to a vote. (I'm quite tempted to do it myself from a position of Devil's Advocate.) Regards, -- Rowan Tommins [IMSoP] --00000000000060abd105aa060019--