Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:103295
MIME-Version: 1.0
References: <CANA3Dev7BXWrThT8DKn=sSfGnYByUUxh_Yk9yqULeA+9c-uwng@mail.gmail.com>
 <CALKiJKpQ3Sd=Q1OgCGrn+v0oQvHXSSB2GMWvHDdKskvz3gm77g@mail.gmail.com> <CANA3DeuGfokS7YgaKTnsQDQO2OASzaTi2OdY8O5mqii-3waDZg@mail.gmail.com>
In-Reply-To: <CANA3DeuGfokS7YgaKTnsQDQO2OASzaTi2OdY8O5mqii-3waDZg@mail.gmail.com>
Date: Mon, 1 Oct 2018 14:27:06 +0200
Message-ID: <CADyq6sKK_7ro7z_TruZqMcETs1P-fW0z_3jwC+nYSo_Og9tsiA@mail.gmail.com>
To: Marcos Passos <marcospassos.com@gmail.com>
Cc: Rowan Collins <rowan.collins@gmail.com>, PHP Internals List <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="0000000000001c8d38057729ed43"
Subject: Re: [PHP-DEV] Class name resolution for \array::class
From: ocramius@gmail.com (Marco Pivetta)

--0000000000001c8d38057729ed43
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

They are still not classes

On Mon, 1 Oct 2018, 14:24 Marcos Passos, <marcospassos.com@gmail.com> wrote=
:

> Rowan, thank you for sharing your thoughts.
>
> You can also see it as a language construct that expects a type at the
> left-hand side of the name resolution operator. In that sense, primitive
> types are perfectly valid.
>
> Regards,
> Marcos
>
> Em seg, 1 de out de 2018 =C3=A0s 05:45, Rowan Collins <rowan.collins@gmai=
l.com>
> escreveu:
>
> > On Mon, 1 Oct 2018 at 00:30, Marcos Passos <marcospassos.com@gmail.com>
> > wrote:
> >
> >> Currently, class name resolution supports all types except an array.
> >> https://3v4l.org/OXFMW
> >>
> >
> > It seems to me that the bug is allowing an expression like "int::class"
> to
> > resolve, when "int" is no longer a legal class name.
> >
> > I suspect the reason "array::class" doesn't work is that it was already=
 a
> > reserved word in PHP 5, whereas other types were legal class names. In
> PHP
> > 5, "int::class" can plausibly resolve to the name of an actual class, b=
ut
> > in PHP 7, it can't, but clearly this part of the grammar wasn't updated
> to
> > reflect that.
> >
> > The parser is being too forgiving here, I think, and should complain if
> > the word before :: is not a valid class name.
> >
> > Regards,
> > --
> > Rowan Collins
> > [IMSoP]
> >
>

--0000000000001c8d38057729ed43--