Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:111152 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 42994 invoked from network); 23 Jul 2020 16:24:35 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 23 Jul 2020 16:24:35 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 0C999180509 for ; Thu, 23 Jul 2020 08:19:19 -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=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-lf1-f65.google.com (mail-lf1-f65.google.com [209.85.167.65]) (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 ; Thu, 23 Jul 2020 08:19:18 -0700 (PDT) Received: by mail-lf1-f65.google.com with SMTP id m15so2808447lfp.7 for ; Thu, 23 Jul 2020 08:19:18 -0700 (PDT) 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=9CkJMWPggDHaOTzoSg57Rp2isnEVEoJNlvsGNHWKaFg=; b=SGUd+fhUTwjg9Ez+c+7K9h9QkvMFmwRTMytoelpJASoOSiScKUEEEDsNAa/M9lgMEE dfEMbbwDsjc1PYPnUmN2sfGI8EyRakkFYMgslSxO0cXyZHs3Q/0u49vZRA9PDBLwD6fa Qoh+9DTHqJLLABqbvmqoh0Lzdm+PBfmyuZV0cDG2PVfohDP7h1Cyk8lDCQtyKjzBP7VL FLohoczw9J2ZR0KVjPCD1T9Q8LQdP9np3k3QQKfULuf8dTw4KBVS+r6Z0k9GxDZdcQy2 picW0+T/WUTbpbK0bGV5/mwo1enSOCvDCUqaOHPO80ikunXYl215wSMy56TPoh/eVW52 ZbVw== X-Gm-Message-State: AOAM532+P9eGZirVOsWCkDs/NjN2KZ31muVm6wZBMPW9ylO0HWqjqmdz aL+a9u5KX6tRugXc9Nq+bculgmwGkCK9zFWR5L/8xg== X-Google-Smtp-Source: ABdhPJzUv6sACinnPmfdYN+xihrjWBUlAVP/Rm5UmWOpNRzlmqqGk6JiMc1fTcEo/FOXws67CbUQHPsh8vo5YjxZr6s= X-Received: by 2002:ac2:5f48:: with SMTP id 8mr2463120lfz.157.1595517553974; Thu, 23 Jul 2020 08:19:13 -0700 (PDT) MIME-Version: 1.0 References: <5f192da8.1c69fb81.1600e.098eSMTPIN_ADDED_MISSING@mx.google.com> In-Reply-To: <5f192da8.1c69fb81.1600e.098eSMTPIN_ADDED_MISSING@mx.google.com> Date: Thu, 23 Jul 2020 10:19:02 -0500 Message-ID: To: Mark Randall Cc: PHP internals Content-Type: multipart/alternative; boundary="00000000000009ba5e05ab1d61fd" Subject: Re: [PHP-DEV] The @@ is terrible, are we sure we're OK with it? From: pollita@php.net (Sara Golemon) --00000000000009ba5e05ab1d61fd Content-Type: text/plain; charset="UTF-8" On Thu, Jul 23, 2020 at 1:26 AM Mark Randall wrote: > On 23/07/2020 02:00, Sara Golemon wrote: > > Regards the vote; I don't believe that @@ has been proven unworkable, > > however if I'm wrong about that, then the second choice selection from > the > > last vote would obviously take precedence. > > I don't believe the concern is that we have something unworkable sitting > in front of us right now, after all if that were the case we would not > be needing to have this conversation as the RFC would already have been > rendered void. > > What we do have, is a deep sense of unease that we collectively made the > wrong decision, based on, in part, incomplete information. > > If that's the case, then the solution still seems obvious: Defer attributes to 8.1. I know a LOT of people will not be happy about that, but it's the most responsible thing to do if the threat of forking up is that present and that dangerous. There are plenty of cool new toys coming in 8.0, we can save something for 8.1 and get it *right* instead of shooting ourselves in the collective foot. -Sara --00000000000009ba5e05ab1d61fd--