Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:117461 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 67660 invoked from network); 30 Mar 2022 13:22:47 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 30 Mar 2022 13:22:47 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id BB7E9180539 for ; Wed, 30 Mar 2022 07:51:16 -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, T_SCC_BODY_TEXT_LINE 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-yb1-f172.google.com (mail-yb1-f172.google.com [209.85.219.172]) (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 ; Wed, 30 Mar 2022 07:51:16 -0700 (PDT) Received: by mail-yb1-f172.google.com with SMTP id y142so37146780ybe.11 for ; Wed, 30 Mar 2022 07:51:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=rO7h+eYf0bPApNe3bRDJWgyQGHAFldqos8OrLlmyUQU=; b=a1T9uK+YFCneJsuNVTiKSW9TDg+2H8Jt+VsANJ6FF1GZtSI8urqe7dl1tYsQz/p3DR qmAV1ZxA8dgKgo+5uDBxqJed+P1Q9wr1NCppBSlvxNDGGw2FYaJjUP7+UgZC7NTcxVfV tHbXqbXy8m7S5VRiqkwDAjPjnrU8nymwqjZeJrwVC8bdfBVKWKvXsLA8qAuhQl3VxrfZ uGwHD9Lh1nunFIikYrV/hZguogcrBjDVqIVg23dNZoTpT2j5ZMbzh/SuSx16/Gs+//xK brw2aPVvgoqsHfBjg3uGfbJ1w0N22kQSVE2QtLzjeQXeaZShTUz/Yfd9iNQcyf49zM68 y8Mw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=rO7h+eYf0bPApNe3bRDJWgyQGHAFldqos8OrLlmyUQU=; b=kuptOIEkReU6bsH7GkqKiwxuhali1+PAOtzL8pjiAbnBE8wouhe1f26N6EahDQDVHv oX0o8DTSNkkEX+0RswvlcXE7aMR09w2wiHTSah+wzAcGSfL4ssEDjsuiKCqbrpe2dNeh aGBubuUo8blrbR6Dd0QXV93MAv0OgHAVQmcLIgQODluUNS8NpsNBd7sJzX8Ld1Bb6HgR c7Gf75hViTkXbJhQgz3AVl+Oy6PrrOPBKvqy4+5PYl9x8wom1n6JtqhcEG0I8n4pgJIr jZnv00qwCuhHRNSUitt+ahoNZjRsBfcSNpx8HSDBcNe2uxQl5NtRZuzChH9DIOkc4m/N tWfg== X-Gm-Message-State: AOAM5312oody8L95Hdiz1KYidaKzEBJw0WBwivi7LusTgbbK2jmnZOtl gHhC8RWX1mZXNh7P2k3g+7acDBWEsJo1+0SnGw== X-Google-Smtp-Source: ABdhPJzdB69/0DS5T4U50RQCjeGF0rZ7DEpD6dvao1eLhJKA+0fYh6wxY2HCgq6lvUTwbcxv8DDKfS0hN6ACYeSHYUE= X-Received: by 2002:a05:6902:102d:b0:639:62f9:a479 with SMTP id x13-20020a056902102d00b0063962f9a479mr29460535ybt.9.1648651875767; Wed, 30 Mar 2022 07:51:15 -0700 (PDT) MIME-Version: 1.0 References: <76c399cb-fb29-4583-a212-8eb69740c96b@www.fastmail.com> In-Reply-To: Date: Wed, 30 Mar 2022 16:51:04 +0200 Message-ID: To: Mark Niebergall Cc: php internals Content-Type: multipart/alternative; boundary="00000000000069da8f05db70ad21" Subject: Re: [PHP-DEV] Typed constants revisited From: guilliam.xavier@gmail.com (Guilliam Xavier) --00000000000069da8f05db70ad21 Content-Type: text/plain; charset="UTF-8" > Ah yes, I hadn't considered expanding this RFC to namespaced and global > constants. Let me mull over implementation syntax for those and include > them in the RFC. My initial reaction is to not include those in this RFC, > keeping the scope to just class constants. If there is value in typing > namespaced and global constants, then another RFC could add those. > Yes, it could be simply a mention in a "Future scope" (or even "Unaffected functionality") section (and the syntax could indeed be a problem, like for typed local/global variables...) > Once I have all these new issues figured out and the RFC updated, I'll > start that new thread. > Looking forward to it =) --00000000000069da8f05db70ad21--