Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:113182 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 34124 invoked from network); 15 Feb 2021 16:18:34 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 15 Feb 2021 16:18:34 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id EE7B41804B1 for ; Mon, 15 Feb 2021 08:05:04 -0800 (PST) X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on php-smtp4.php.net X-Spam-Level: *** X-Spam-Status: No, score=3.2 required=5.0 tests=BAYES_40, HEADER_FROM_DIFFERENT_DOMAINS,HTML_MESSAGE,RCVD_IN_DNSWL_NONE, RCVD_IN_MSPIKE_H2,SPF_HELO_NONE,SPF_SOFTFAIL autolearn=no autolearn_force=no version=3.4.2 X-Spam-Virus: No X-Envelope-From: Received: from mail-lj1-f176.google.com (mail-lj1-f176.google.com [209.85.208.176]) (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, 15 Feb 2021 08:05:03 -0800 (PST) Received: by mail-lj1-f176.google.com with SMTP id v6so8388501ljh.9 for ; Mon, 15 Feb 2021 08:05:03 -0800 (PST) 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=lCWcCrgy303B6vtJxo/ijhwhWeHbQJlGllSUeBHFCSY=; b=rWIWfj0JdRr592HQfwUisqc2TGnscLb03U7D7XLL+/1guUqZeKPl9zJ9pmAm0k6Ybq 9QhI6HKhffINeEAw3/xj205QYf4jg2SCYvS3Fm11wahiO+K/rkC4cqjyD83jrc7yTd2c sFeSjMDmyJqikuiXG0XJ32P5nzIykDwRCShctlewXLQocIoEoVmCgCycKziQx5ltic5O TlMcCp8OHwGkdJiPuCVUiRmlxHf2MMPdaxZeVLjCYkfncIbBHaG6vmV4lVaXFMGxRj1G 90KAAJXXgAgnbdDffebEcgA3W03FusjN6XZtlQVu3twFOQE7xuWL2vxwuK+Cz6lUs9mE UVGw== X-Gm-Message-State: AOAM532zSprRP9GDToYRSnYHNud80TspHTPc7E4RU24zXYE2h+vpcWTi sZTsOR/Uclx6mQdD+BUFVCUHmx6A21nh3nkoxqzGxg== X-Google-Smtp-Source: ABdhPJwm0Pf3ivq0Cox5tTFMtN/HuaGJtd788SzFeWR51e/uX0/war7cQxp7+uZRzJ7MZRZ5qB8xawURkQSSuUf7/5s= X-Received: by 2002:a2e:2a83:: with SMTP id q125mr9886477ljq.244.1613405101264; Mon, 15 Feb 2021 08:05:01 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: Date: Mon, 15 Feb 2021 10:04:50 -0600 Message-ID: To: Matthew Brown Cc: Stephen Reay , Internals Content-Type: multipart/alternative; boundary="000000000000f0a5bf05bb622560" Subject: Re: [PHP-DEV] Whitespace around Paamayim Nekudotayim (double colon) From: pollita@php.net (Sara Golemon) --000000000000f0a5bf05bb622560 Content-Type: text/plain; charset="UTF-8" On Mon, Feb 15, 2021 at 8:53 AM Matthew Brown wrote: > > There are plenty of places where PHP doesn't allow whitespace currently. > > The most comparable example is between namespace separators: > > Ns \ bar(); > Ns \ SOME_CONST; > That change was made very recently (8.0) and was done for technical reasons (attributes) not aesthetic ones. Personally, I agree that adding whitespace around double colon is a suspect move, but breaking valid code for the sake of one's own sense of aesthetic doesn't progress the language, it regresses it. -Sara TL;DR - I vote No to such a change --000000000000f0a5bf05bb622560--