Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:111251 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 27262 invoked from network); 29 Jul 2020 18:49:55 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 29 Jul 2020 18:49:55 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 2221A180510 for ; Wed, 29 Jul 2020 10:46:09 -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,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-oi1-f171.google.com (mail-oi1-f171.google.com [209.85.167.171]) (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, 29 Jul 2020 10:46:08 -0700 (PDT) Received: by mail-oi1-f171.google.com with SMTP id j7so5060056oij.9 for ; Wed, 29 Jul 2020 10:46:08 -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=BAJzFpnQQ/26XzyArL0M2cQJ+ST2vEWu3HZ1S8/Nwag=; b=IGbWD9696PyYS3+Aio4bzgru7A83t5VWNKLUGQF1927lSzVcgRB3apCC+rPTgBslAv YsXhk21ygoZG3ms1wvH91w4biLUe1Jy0d0lw6urdWf4/lbunzTq4GU5UCPTzJjRiVFNB yp+46JX+vHS3TOYfzCs0SgnBDt8SqqkVmAtN0Rq9J8KlADTudpW9sCqj/fzeePxToeXS c6EWxiYS7o4zs+eHvTZdpZQGtdua1twEv05HwpQ85UDp6zSpUdBPGwFsVp6km0gz+jxn UGFsmsYPmxb8T32ebxQ0at2x8h7FEXg1E8k3BrrKElY8KEytzg+Yy0qWPGdMt72qrYGo MLXA== 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=BAJzFpnQQ/26XzyArL0M2cQJ+ST2vEWu3HZ1S8/Nwag=; b=rgvZ17RAKvnJntMru9ayOP/hsZNcVRXv9P1g4XrdUtQkCFCZVHv0MnM/ofYwNOR2GO qK868DXTuxxa9/R4Ob6YPIo+7VUS299ttbApSL9107YBuK9NIA1hcQrEKmX0hfVF+EE7 uNPC8WwcPO6RKkdKNY0AOSDf5mofNJQ9AElhLd2YFiE5Dnkk/0FJ+8jv1fUg/BCOuhmr dzykrE2oTDCygUFjKQ4xPBL2KM7rxuZ8XJ0cgm+rR2drK0ETbP6wLDlF14DjYe4Mz7N9 dotIZDd/w2o7ZZbCpUDy/sYvRtu/QoMlzyRy90v16kMP03f+ZRFXteDgOF/31QWTPeGM YHnA== X-Gm-Message-State: AOAM533B4o2a2QKCOQbvjDBYJb4zwL6qXQc9nuyvfxUBh23+KDaAUr/a ONeZdyC/lqJIkuMWjEfxQV0pFTmrkzFXOdFBO1A= X-Google-Smtp-Source: ABdhPJzIWgiBrX526a7naS82/s6z24+0IyAA6Z/J1hwuOEaKCuIKfFlDQupkibE5OlqKMJ+piv9cD9yrfPNpnIlj+KI= X-Received: by 2002:a05:6808:aa2:: with SMTP id r2mr8547758oij.162.1596044760815; Wed, 29 Jul 2020 10:46:00 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: Date: Wed, 29 Jul 2020 14:45:46 -0300 Message-ID: To: Nikita Popov Cc: PHP Internals Content-Type: multipart/alternative; boundary="000000000000039af605ab98217d" Subject: Re: [PHP-DEV] Allow two words keywords From: david.proweb@gmail.com (David Rodrigues) --000000000000039af605ab98217d Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Oh, you are right! "yield from" is not common for me currently, so I really skipped it. In this case, is there some problem to apply it to Attribute case? "using attribute(Attribute())" or something like that? Atenciosamente, David Rodrigues Em qua., 29 de jul. de 2020 =C3=A0s 14:01, Nikita Popov escreveu: > On Wed, Jul 29, 2020 at 6:50 PM David Rodrigues > wrote: > >> Hello! >> >> I do not know if there is some consensus about "why not use two words as= a >> single keyword" in programming language in general, but I really found a >> few examples of it, as in SQL with "GROUP BY", for instance. >> >> So I question if it could be used on PHP to expand the keywords repertoi= re >> by mixing two words without causes BC. >> >> I will use the Attribute syntax-war to exemplify. >> >> I really prefer to create a new keyword "attr()" or "attribute()" to mak= e >> attributes possible. It basically uses the same function-like with >> arguments to work. But it invariably will cause BC to old codes that use >> attr or attribute names (eg. "function attr()"). >> >> But, if we create a new two-words keyword like "using attr()", maybe it >> will not cause any BC, because "function using attr()" is impossible, bu= t >> "using attr(X) function attr()" will do. >> >> I do not know if I am being high with peanuts, but maybe it could be >> considered to this discussion and make possible new features on PHP >> without >> creating strange symbols like @@ or #[] that will requires that new user= s >> check the documentation about "what it mean", while is very hard to Goog= le >> symbols (so search will be "what mean double at in PHP" or "what mean >> hashtag brackets"). >> >> >> Atenciosamente, >> David Rodrigues >> > > PHP does have a two word keyword: "yield from" > > Nikita > --000000000000039af605ab98217d--