Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:111136 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 79015 invoked from network); 22 Jul 2020 20:57:09 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 22 Jul 2020 20:57:09 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 6D9C8180509 for ; Wed, 22 Jul 2020 12:51: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, 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-pf1-f170.google.com (mail-pf1-f170.google.com [209.85.210.170]) (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, 22 Jul 2020 12:51:39 -0700 (PDT) Received: by mail-pf1-f170.google.com with SMTP id t11so1818815pfq.11 for ; Wed, 22 Jul 2020 12:51:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=vOGd8SQqvWOdPSEkO9SP7/q8CW6Abwn1ciLbqB7iKdQ=; b=VS6VSQiQDl3XjRVuoJS3eC+F4sXre9GQ5ADozRkNPe7ZSSdyfHD2NIupawJU3H2amG 7cA9H3GWwuURdnEXfQxBhJ8PubS4R97+P+6tM1+cUBSziZ3xcHmrbg57pu4K3PZdLKR6 rJTILImGvUU4dQsmFK2TU3aCJlWzqU1WQCci2n6UmT8n2x2ciJJ4+4zl+MSpt8+LgDhp ZnGod++EEV/xOgpeEyH795fJGE2WtXjBFoXMao+yEj3pZ4uDLdUrAZ8BUyAObF+cXMip TZvXanrctLdzK4YSqLD1KTQ8TtxqxiKIOZJjuxQXFXl0N7OfV/eALBVlpV1p+smJNAtr eK1Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=vOGd8SQqvWOdPSEkO9SP7/q8CW6Abwn1ciLbqB7iKdQ=; b=K+UNduxhyqTjmnFGcjgVKZwCmMxOERXnFvFn2xDxzCm6dwa9PHo9YZpWqpqfdVqakX XZT0xERia11p/dHyIrrcNlgfnQVNG9vXTKYLWEAiPHFpfAzdCxYdlmy2Thu67gWSXmFB 162QW9ZGEupqNS4Ku0Q/4o2jshxl5hlzAvu6PQCq0CtDkxU6o8l58oOhKHZb8ZF2elj0 Hi2yObExkty9e9AR3V8QGH5rlk+FV9RqgYhg2nPalRg27eJsPUSOy3MUozREm9HHYo4T hhj+lEYOzFs/sTQ/joeL5XGwldCj5WUjWfXc7bPrpDTZXraXApHBuXmvG6tDhtRSP50o CNkQ== X-Gm-Message-State: AOAM530wGWtxVHpqrsBDMIHQ9rr08/olfKmB1Nm5+8LcgN4ZltBEss6p 4vH7JG9IacqT+AqjgUE1IK1Ds4OY1w== X-Google-Smtp-Source: ABdhPJxVov4yNfpRDPrBFSmmywrgboEhs4MBHIxXFY7OOrE29jfPUmqgZIZwbnn8Hd208YKlsX2pig== X-Received: by 2002:a62:1acc:: with SMTP id a195mr1093677pfa.32.1595447496041; Wed, 22 Jul 2020 12:51:36 -0700 (PDT) Received: from Stas-Mac-3.local (ec2-34-209-88-149.us-west-2.compute.amazonaws.com. [34.209.88.149]) by smtp.gmail.com with ESMTPSA id 66sm431926pfg.63.2020.07.22.12.51.34 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 22 Jul 2020 12:51:35 -0700 (PDT) To: Derick Rethans , PHP Developers Mailing List References: Message-ID: <1fa0db88-40d1-ff90-03bb-c9b8325ce61d@gmail.com> Date: Wed, 22 Jul 2020 12:51:33 -0700 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:68.0) Gecko/20100101 Thunderbird/68.10.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] The @@ is terrible, are we sure we're OK with it? From: smalyshev@gmail.com (Stanislav Malyshev) Hi! > I know we've voted twice on this already, but are we really sure that > the @@ syntax is a good idea? I think it's not a very good idea, and <<>> was just fine, but a lot of folks apparently voted for it. Would be nice to see their opinion and how they answer your concerns. I'm not sure it's proper to override the vote unless there are some severe technical concerns that make that choice impossible. -- Stas Malyshev smalyshev@gmail.com