Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:111470 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 67576 invoked from network); 11 Aug 2020 16:08:03 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 11 Aug 2020 16:08:03 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 368A51804D9 for ; Tue, 11 Aug 2020 08:07:30 -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-ot1-f41.google.com (mail-ot1-f41.google.com [209.85.210.41]) (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 ; Tue, 11 Aug 2020 08:07:29 -0700 (PDT) Received: by mail-ot1-f41.google.com with SMTP id h16so10342944oti.7 for ; Tue, 11 Aug 2020 08:07:29 -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=RptJ8Tp7V+EhPstGmWTPifFxCG4zkhIbs9vOEl/rC74=; b=TzFvLHTboIglMCEQfGRZ2EtdypCLtugZtuFtcqsG5fnCtWZnmXI7au2VpPRv/HqZfi Fyk1nGGV/QvynuClfcRSb+yQJ4SbPV8NtpiFnAIr3t2y+Z/6xqrtjhsKuw2w6z3WqOH4 mUP/fGQ2UB4L/Sh8PdQXksMuB02mkR0q2GpC7Mgi3mcjXelnvPyhET7YPhPahPF0A2pC gZa4Q2Bj2MGHIe9l9WqIcdu4JCL65BszHV8LmKLv1onn3OiiLzApBtYlmHbxkWFoWy8I EY2Vf4qAaX8noyew2LWdMF2qOt35oWhXTA+iJkJzywmAuuydsFlb0qWHBH0NMzRFtVJL 4lTw== 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=RptJ8Tp7V+EhPstGmWTPifFxCG4zkhIbs9vOEl/rC74=; b=teSe0JLCUbQTKVOHMReoYNhlLwxcQ9sgJ6ibwHY/hk5V5XCmG001p26FaeIn0+z3Gh iOOlgt/oCz3W6+yMp8+0MgHWRfvCBwRKrVycdmdHJv5M1ragkVs+1IIlGH7AgdrfKaK5 sBx9JI3jtn3jhBxUQUZyQtiqHyy24ns2463DNFCxwVzjq69Lw+D7bN+1JzVwa3z7g7Pg SgX2ObTMTeeEXNuthmLGdwjFQSC4g1MmQEtZhfKuk1r2B+PQqL5UQcm5HSAGTN9Q3H4U E/N75IxUVb2dz8Rf/mBqnOhV1xmTATzZZXbJWpNwNf/VGqjQU3gzTo/B7XI0SYQtRyiB pLow== X-Gm-Message-State: AOAM530IRF7uQaIbO5iBqGmBcYxFytj3Gzx5Zem93Y4AjL5Qlem55/gi VNfZ4Bd6MxPLbbOi0hgtogNwdiRbOQkuIlTOnfs= X-Google-Smtp-Source: ABdhPJyDN6pKJVZrfDMxNDeMFZTLmvjpjsHvtZMCT+JVuR0tLTOdutVlrou1oedfQ2ZYQk7GFIJxOZb/AqS9uFoOHx8= X-Received: by 2002:a05:6830:1db1:: with SMTP id z17mr5538457oti.170.1597158447977; Tue, 11 Aug 2020 08:07:27 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: Date: Tue, 11 Aug 2020 11:07:17 -0400 Message-ID: To: Sara Golemon Cc: Derick Rethans , PHP Developers Mailing List Content-Type: text/plain; charset="UTF-8" Subject: Re: [PHP-DEV] [VOTE] Shorter Attribute Syntax Change From: guilhermeblanco@gmail.com ("guilhermeblanco@gmail.com") Hi Sara, I'd like to explain my rationale. Most of the time I end up using "#[todo] Whatever" while documenting my code... my intentions are "# [todo] ...", but you know... missing that space char doesn't break anything today... In any case, BC is broken and FC would also not work. Now I assume it's a quite rare scenario where someone is doing: @[...] where suppressing is needed, especially when we check against the #[...] case. Cheers, On Tue, Aug 11, 2020 at 10:55 AM Sara Golemon wrote: > > On Mon, Aug 10, 2020 at 3:41 AM Derick Rethans wrote: > > > https://wiki.php.net/rfc/shorter_attribute_syntax_change#voting > > > > > Just chiming in to say all, y'all voting for @[...] are making a terrible > choice, and are you sure you're okay with it? > > We have options with varying degrees of backward compatibility issues (<<>> > none, @@ some, #[..] and @[..] a bit more than some), and only one which > offers forward compatibility (#[..]). > So why vote in favor of the option with the highest BC breaking probability > and no FC? > > Thank you for coming to my TED talk. > > -Sara -- Guilherme Blanco SVP Technology at Statflo Inc. Mobile: +1 647 232 5599