Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:111258
MIME-Version: 1.0
References: <CAEsg9X2d2Cq_3rA1boA9rCi1brqV9Jw9XYU_eL5W6cYXNd4YdA@mail.gmail.com>
 <CAF+90c8nDPxOPmnV8RHT7Wi-GUyqttCiXmRNezw+TH=azhsTxA@mail.gmail.com> <CAEsg9X3P4Q-NZzuUh6Om4_zF8GDH+SieKTS-no++LFsKEgWPCg@mail.gmail.com>
In-Reply-To: <CAEsg9X3P4Q-NZzuUh6Om4_zF8GDH+SieKTS-no++LFsKEgWPCg@mail.gmail.com>
Date: Thu, 30 Jul 2020 11:49:46 +0200
Message-ID: <CADK1yXKHp3sS8RjGgbfmtWf_zVMqrmYsQ5fCrnX7tWmgzAMU8Q@mail.gmail.com>
To: David Rodrigues <david.proweb@gmail.com>
Cc: Nikita Popov <nikita.ppv@gmail.com>, PHP Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000537df205aba598ac"
Subject: Re: [PHP-DEV] Allow two words keywords
From: deleugyn@gmail.com (Deleu)

--000000000000537df205aba598ac
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Such a nice syntax. Even better than @@ and @. I wish this could get more
attention/traction.

On Wed, Jul 29, 2020, 19:46 David Rodrigues <david.proweb@gmail.com> wrote:

> Oh, you are right! "yield from" is not common for me currently, so I real=
ly
> 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 <nikita.ppv@gmail=
.com>
> escreveu:
>
> > On Wed, Jul 29, 2020 at 6:50 PM David Rodrigues <david.proweb@gmail.com=
>
> > 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
> repertoire
> >> 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
> make
> >> attributes possible. It basically uses the same function-like with
> >> arguments to work. But it invariably will cause BC to old codes that u=
se
> >> attr or attribute names (eg. "function attr()").
> >>
> >> But, if we create a new two-words keyword like "using attr()", maybe i=
t
> >> will not cause any BC, because "function using attr()" is impossible,
> but
> >> "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
> users
> >> check the documentation about "what it mean", while is very hard to
> Google
> >> 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
> >
>

--000000000000537df205aba598ac--