Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:113615 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 78966 invoked from network); 19 Mar 2021 14:38:11 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 19 Mar 2021 14:38:11 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id D6E4F1804E4 for ; Fri, 19 Mar 2021 07:32:42 -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_H3,RCVD_IN_MSPIKE_WL,SPF_HELO_NONE, SPF_PASS autolearn=no autolearn_force=no version=3.4.2 X-Spam-Virus: No X-Envelope-From: Received: from mail-ej1-f54.google.com (mail-ej1-f54.google.com [209.85.218.54]) (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 ; Fri, 19 Mar 2021 07:32:42 -0700 (PDT) Received: by mail-ej1-f54.google.com with SMTP id u9so10065276ejj.7 for ; Fri, 19 Mar 2021 07:32:42 -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 :cc; bh=iJ4Q4ir8+OxV0M7WDBB393kbPWMZQ6VKnHLobaLOOrw=; b=RPO3z9eAZ/tWHNGaLHljEUV9muDvsqm+3qjIQyqQsP1oI45vZjKeY1q1k+yiB3PZP0 61ZTbfiXLjGuQ9q/Ri6w/Tk1uLUTeoKcSebRZ95ZyLGCVYpnLuCl8ww2aXb87cPOMSxa m8GxdrWdGBXTiap/Jv+HGJ9rvAb7Uts4VqhRFJiSj+IBi8ErULUqPDCxbU1bUduOxc5t 1BFqkMUzM/0UeC9BwHUg92PxZsJ7HjsYwJxd8mPgxi8qNjNRk/LFx+FvBGtD/z0nqxnv MhT8dODAFQRyHEfa+nRATp7IPXbq1npVmBxubOAxcOR3T1MtpK+RLQdKLY5nRXLKfnCp INcQ== 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:cc; bh=iJ4Q4ir8+OxV0M7WDBB393kbPWMZQ6VKnHLobaLOOrw=; b=qMKw+t0xxuUan4Q9q5f4jvyU/Pt3Uv3LQasMY42qK0RBithdqbCzSJtL/baKUh7KzS 63plmTqtJ9A0RdB3StWaP+pb6LtcMTJHNs6Wya2XXNmV+8V5UN3aFk2oG+IxK+wq3XyF U78UVMqNiO97cLPPLYhbOa1w2XJE6iAjzs2JrrnuPzZZ5bn4LgIrmOVxAtBWSyQf1e4N q0AcUsGKdBRKPQstFfL8K7X9+dCdERlDkdgD/UtEMgj1zOKQt35/hOL+Jta8a2AV89oi 28Be7vXDLlC8lPX+74B6VFPbrSv/lLYE6fOWdTGsyTOkwNuUDcZ9Ev1b2qrU86jPFdMZ 2OmQ== X-Gm-Message-State: AOAM531oZNfcMvT3YYl/v18aCcDa/zFXRq4KFePU+MEQzkkYMj5Ri1C0 UEgQwqxdKvLkRAQZ5L3fwXLIZbX/WdXwjXGe0z92qmxg8+Z+Ag== X-Google-Smtp-Source: ABdhPJxTSXt9V8C2sdYCWfeaASlxWUn9fxKaWkAHlUjtVLMW+/Oj2jN1G/FuHV+HxBUpcUb6UdHWEwEyYTVuvtu81zg= X-Received: by 2002:a17:906:fcd2:: with SMTP id qx18mr4563435ejb.327.1616164359778; Fri, 19 Mar 2021 07:32:39 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: Date: Fri, 19 Mar 2021 14:32:28 +0000 Message-ID: To: Nikita Popov Cc: PHP internals Content-Type: multipart/alternative; boundary="00000000000090327a05bde496f5" Subject: Re: [PHP-DEV] [RFC] Namespaced in bundled extensions From: george.banyard@gmail.com ("G. P. B.") --00000000000090327a05bde496f5 Content-Type: text/plain; charset="UTF-8" On Thu, 25 Feb 2021 at 20:26, Nikita Popov wrote: > Hi internals, > > The question of namespaces in the stdlib has been coming up a lot recently, > so I'd like to present my own stab at resolving this question: > > https://wiki.php.net/rfc/namespaces_in_bundled_extensions > > Relative to a number of previous (declined) proposals, the main difference > is that I do not propose a top-level "PHP\" vendor namespace, and instead > recommend the use of "ExtName\", in line with existing practice for > extensions. I believe this addresses the primary concern with previous > proposals. > > Regards, > Nikita > As one of the co-authors of one of the previously declined RFCs [1] and author of the CSV extension, [2] where I changed from using prefixed functions to a global class called CSV in the same fashion as FFI, I quite like this proposal, and have no issue changing it to conform to the RFC. This sidesteps the issue of the PHP namespace in a very elegant way by not creating a weird dichotomy for "core" (core/standard/SPL) functions, if some of them start using namespaces as they'll only be one level deep and the name is relevant to the functionality they provide. Best regards, George P. Banyard [1] https://wiki.php.net/rfc/php-namespace-in-core [2] https://gitlab.com/Girgias/csv-php-extension/-/commit/dc48b449543b07eaeff575bd143350693f808d74 --00000000000090327a05bde496f5--