Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:111122 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 23527 invoked from network); 22 Jul 2020 15:51:49 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 22 Jul 2020 15:51:49 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 713111804E6 for ; Wed, 22 Jul 2020 07:46:14 -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=-1.9 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,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-Virus: No X-Envelope-From: Received: from mail-io1-f41.google.com (mail-io1-f41.google.com [209.85.166.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 ; Wed, 22 Jul 2020 07:46:14 -0700 (PDT) Received: by mail-io1-f41.google.com with SMTP id q74so2840396iod.1 for ; Wed, 22 Jul 2020 07:46:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joeferguson-me.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=hBM7P45xwHfr28cBhpu1uqOIiPy6xFUw9hxYIsiPqZw=; b=aEK/oBxxASoNXuUS+1l9zv6GvdpPEG/9vck3muDMLnsdjX08N294jrIsjCuEgqLbXt OF+gDb55qV8z9nUPmnAWRpJaPIuI++c9ojxEnypGdOnOpUu0MEbgTZJJs1buKSN60bnu 86jVeh4a1PFaXJsxhdTK70EWRTRguWa/r3siep3e7UqwHNSkN8+kCNWyvo/xZxjwEGNY +62KnUaKmFQVtnjMX//sUbnJ2YBl16LYr7zRAoUXCNKwAQncaZ5qwpio/wggDdJmR9+o Z2vKJu0P/EZbC8EFVluwou5pDoVuVEmcbVhI/8hBgNXZF8ojdiWj8Ym3YvAnPbvkPu67 suKQ== 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=hBM7P45xwHfr28cBhpu1uqOIiPy6xFUw9hxYIsiPqZw=; b=UJZW7bqOaciO6l6faOuKrWKDseBtSorvaZmXij2XL5WMujO53h/a/ee49JImPFrS9e CeZWEPFAwCZS6hHGP0xS0Wv0Yd2oKUyXH58dgxtBOE+9e5s+0u6WvHIbVc7r8n9kzgLE 3HmaTjUpwGa7wWERM9djoYuyig9otPKtZ54pqGPSbc4Hg0znrDMC5f0um4yWlCTtNg7r PLJccbpVpy3aNYhyUhmMGM6EUGyViKUDfqdiRHnafFuNQPVmXnzy+LwiZAGqg1WxM07d hXdgnZ6q20LArs36v5RnLewvdFluXQVQs7Ty9VkipX01gS1GMWlKYkbhyfboMH7ClWxs 22yQ== X-Gm-Message-State: AOAM531Y/Bq9pxnYnMK2LWkGiaSumRs8YoZAmMjA8Gp73htErlxjqG+X yq4dCtYrg3LJFcxdIVyoWrlrb0d70pC9JlMuJrG7TQ== X-Google-Smtp-Source: ABdhPJxhhBaybdAG6tRk1HrZUdNjUHseoFZXTilDikf2lAl1IzyWy1rSrswGSJuYDbHQQhNEaaMdH8uwOK5oSGM2fAo= X-Received: by 2002:a6b:6511:: with SMTP id z17mr128929iob.104.1595429173443; Wed, 22 Jul 2020 07:46:13 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: Date: Wed, 22 Jul 2020 09:45:35 -0500 Message-ID: To: Gabriel Caruso Cc: Derick Rethans , PHP Developers Mailing List , Sara Golemon Content-Type: multipart/alternative; boundary="00000000000025da4705ab08cde1" Subject: Re: [PHP-DEV] The @@ is terrible, are we sure we're OK with it? From: joe@joeferguson.me (Joe Ferguson) --00000000000025da4705ab08cde1 Content-Type: text/plain; charset="UTF-8" Hello, Internals, I would be happy to author an RFC on replacing @@ with #[] but based on Larry's comments it sounds like the weighted voting already solved this issue for us? We as internals just need to decide that @@ isn't a solution and defer to the next ranked vote? I'd be the first one to +1. On Wed, Jul 22, 2020 at 9:38 AM Gabriel Caruso wrote: > On Wed, 22 Jul 2020 at 14:00, Derick Rethans wrote: > > > Hi all, > > > > I know we've voted twice on this already, but are we really sure that > > the @@ syntax is a good idea? > > > > - There are lots of grumbles, both on here, room 11, as well as in the > > wider community (https://www.reddit.com/r/PHP/comments/hjpu79/it_is/) > > - It has the distinct possibility to cause further parsing issues, akin > > to what ended up happening with what Nikita is addressing at > > https://wiki.php.net/rfc/namespaced_names_as_token > > - There is no "end symbol" to make finding occurences easier. > > - It is a syntax *no other language* uses. > > - @ is never going to go away, so the possibility of @@ moving to @ is > > also 0. > > > > Please, let's do the sensible and use the Rusty #[...] syntax. > > > > cheers, > > Derick > > > > -- > > PHP 7.4 Release Manager > > Host of PHP Internals News: https://phpinternals.news > > Like Xdebug? Consider supporting me: https://xdebug.org/support > > https://derickrethans.nl | https://xdebug.org | https://dram.io > > twitter: @derickr and @xdebug > > > > -- > > PHP Internals - PHP Runtime Development Mailing List > > To unsubscribe, visit: https://www.php.net/unsub.php > > > > > Hello Derick. > > I do understand your concerns, and I appreciate that you've reached out. > > Although we are very close to the Feature Freeze date for PHP 8.0 ( > https://wiki.php.net/todo/php80), I wouldn't mind opening an exception for > this specific case and let you (or someone), create an RFC proposing to > change the syntax of Attributes (https://wiki.php.net/rfc/attributes_v2), > and that only! > > I'm copying PHP 8.0's Release Manager Sara, to hear her opinion on this as > well. > > -- Gabriel Caruso > -- - Joe Ferguson JoeFerguson.me osmihelp.org --00000000000025da4705ab08cde1--