Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:109864 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 38946 invoked from network); 27 Apr 2020 23:46:43 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 27 Apr 2020 23:46:43 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 750161804B4 for ; Mon, 27 Apr 2020 15:19: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_H2,SPF_HELO_NONE,SPF_PASS 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-io1-f49.google.com (mail-io1-f49.google.com [209.85.166.49]) (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 ; Mon, 27 Apr 2020 15:19:41 -0700 (PDT) Received: by mail-io1-f49.google.com with SMTP id z2so20690197iol.11 for ; Mon, 27 Apr 2020 15:19:41 -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=aqnJAa3Tq72Uw3uiRjJqYEq0B5rfM0iygx+84eXwfJk=; b=XXZ+4EOHys4g0SxWaDL6B3cSmRTpIyAS6JeHiNaNXYZ8q0trA3/XGCUfa/aVj0+GFl +dsaQNOEDyxsfLYEqQ1PwT0hE+pOW0Kl258uEKXLadOj/v2yQzSGhqe7dGkQHkJ/MhVH aWhL7tk2yf5NlK1ceRoF7qC/ZP4fwzb3FqY9XmC4be7XwxbN5WHdGilNLz8ATr8PSprZ 5bYqHBpE46nqPh5yW9ep0pIQYOrDPQgvwiiMhF4vTLqpFNV+hVkzSHcx9tgoH28SPHct f2NSH3IiPrbrJY7XA2VdS5emWZB1PizDt2ffHZKaYkhHyLvOMq+m2XQ6yO/pf0WWVckZ yyAA== 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=aqnJAa3Tq72Uw3uiRjJqYEq0B5rfM0iygx+84eXwfJk=; b=U2Vyx/XhwQYJVk5SjgGCNZSsFtTBU3Sn/0WyV18q6VfaGi4FUH/8foehtm5zoS/F7m NHMWtUaIgEEbQbws1K5T6umUaTZ+oHemje3fTCrhISsxSgkvAj+0G0PD9p2AjEtVVq8k sjTUis7LHggHNY6uoOpSvibERvMMO6gpMDz56znOcnj7b0TqNEXqF5eSBqzmLfB4yfcV AihHLJLn9WORrQDdNrDpet69wsdxFXMm7umrq43ECoyC8ghWUo9rBcTvGbhpyy/xNupz 9zWaF9f1KHgrRVEFrM+rYIZVsiCh8hLiplqbJOCF6lGD7xNtNn2AyZViTNCaJqCVqvoz kvFQ== X-Gm-Message-State: AGi0PubqIEC6hfI9o4AHlmJjKnt/02vCcNNCrKafDrDGHQOywqo9wsJN j2vb3I0ZFeMqJlO6ynVCT5dQCiGCxCG+YYWoDOo= X-Google-Smtp-Source: APiQypJPD788XFQtMGvBJsHMGOZxhF1ZVVikYe8St76UeWA1W6yi5OJfU8AtEboIW+qhYAthdIQjb0XdnhVcESpbJQI= X-Received: by 2002:a5d:9494:: with SMTP id v20mr23298873ioj.101.1588025981276; Mon, 27 Apr 2020 15:19:41 -0700 (PDT) MIME-Version: 1.0 References: <5ea5e72d.1c69fb81.ecd6b.8d05SMTPIN_ADDED_MISSING@mx.google.com> In-Reply-To: Date: Tue, 28 Apr 2020 01:19:30 +0300 Message-ID: To: Rowan Tommins Cc: PHP internals Content-Type: multipart/alternative; boundary="00000000000082151105a44d1c26" Subject: Re: [PHP-DEV] Re: [RFC] PHP Namespace Policy From: maxsem.wiki@gmail.com (Max Semenik) --00000000000082151105a44d1c26 Content-Type: text/plain; charset="UTF-8" On Mon, Apr 27, 2020 at 11:26 AM Rowan Tommins wrote: > To me, the answer to that is quite simple: we have several hundred > functions, and several dozen classes and interfaces, which are not in such > a namespace; and we have millions of lines of code out in the world using > them. So either we need a strong rationale and a concrete plan to move all > of those into the namespace, or we need a consistent policy on what goes in > and what stays out. To me as an end-user, the ability to write readable code is as important as ability to write code that performs well and is well-tested. All these prefixes, like PhpAttribute being discussed right now, only decrease readability. I'd rather have to import \PHP\Attribute or use plain ol' \Attribute but no prefixes pretty please. I know they can be renamed locally via `use PhpFoo as Foo;` but that's a kludge. > It wouldn't make much sense, for instance, to have > PHP\str_contains but no plan to move str_replace. We don't have to mix namespaced and non-namespaced stuff within the same area, thus all str* functions should remain unnamespaced, and honestly I personally don't care if _functions_ are in \ or \PHP. I, however, would love if no new classes in PHP were prefixed. -- Best regards, Max Semenik --00000000000082151105a44d1c26--