June 27, 2020 14:email@example.com (Rowan Tommins)
On 27/06/2020 10:56, Andrea Faulds wrote:
> Of course, if T_PAAMAYIM_NEKUDOTAYIM was never encountered by userland
> developers, this RFC wouldn't exist. The thing is, I don't think
> T_DOUBLE_COLON should be encountered by userland developers either â
> in my view, as an implementation detail, token names shouldn't be part
> of parser error messages at all. If we were to remove token names from
> the parser errors, we would avoid the problem this RFC seeks to solve.
> For most tokens we could simply display the characters it corresponds
> to (e.g. "::" for T_PAAMAYIM_NEKUDOTAYIM, which we already do!), and
> for those with variable content (e.g. T_STRING) we could display a
> human-readable description of what is expected (e.g. "an identifier").