Hello Internals
The voting has closed with 44 for and 30 against. The RFC has not been
accepted as it did not meet the 2/3 requirement to be approved, thank
you to everyone for joining the discussions and turned out to vote.
--
regards,
Kalle Sommer Nielsen
ka...@php.net
--
PHP Internals -
> Le 28 juin 2020 à 00:53, G. P. B. a écrit :
>
> My perception is that most of the community finds it baffling why anyone
> would be against this change.
>
What baffles me, is the amount of discussion around changing the name of ONE
token, whereas it is clear that a bunch of tokens (a few
On 27/06/2020 23:53, G. P. B. wrote:
[...] there are only 3 parse errors which have the added
information of what the token represents, namely T_SL, T_SR, and
T_PAAMAYIM_NEKUDOTAYIM.
I'm not sure what you mean by there being only three. Since PHP 5.4, all
parser errors include the content
Hi!
> Better error messages are obviously better than just replacing the name of
> the token, however this argument is saying that because this isn't perfect
> let's do nothing.
I don't think this is the argument. I think the argument is rather than
half-fix the problem wrong way, let's fully
Hello Andrea, Benjamin, and others,
Better error messages are obviously better than just replacing the name of
the token, however this argument is saying that because this isn't perfect
let's do nothing.
I wasn't aware that Rowan had made good progress on his patch, however, if
this patch needs
On Sat, 27 Jun 2020 at 11:20, Benjamin Eberlei wrote:
> 1. The token name has historic value and should be preserved as such
I don't think it has historic value. It might have nostalgic value but
nostalgia for:
> I think everyone hits it once or twice, has the "wtf?" moment, googles, and
>
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
Hi again,
A further and perhaps more important thought: I think the token names
are actually the least confusing part of parser errors, even for the
famous T_PAAMAYIM_NEKUDOTAYIM. Changing it to T_DOUBLE_COLON may not
help much, because the parser only tells you what the next token it
On Sat, Jun 27, 2020 at 11:57 AM Andrea Faulds wrote:
> Hi,
>
> G. P. B. wrote:
> > https://wiki.php.net/rfc/rename-double-colon-token
>
> I have voted No to this, and I hope I can convince some others to do the
> same.
>
> T_PAAMAYIM_NEKUDOTAYIM is such a famous token that there is probably
>
On Sat, Jun 27, 2020 at 11:57 AM Andrea Faulds wrote:
> Hi,
>
> G. P. B. wrote:
> > https://wiki.php.net/rfc/rename-double-colon-token
>
> I have voted No to this, and I hope I can convince some others to do the
> same.
>
> T_PAAMAYIM_NEKUDOTAYIM is such a famous token that there is probably
>
Hi,
G. P. B. wrote:
https://wiki.php.net/rfc/rename-double-colon-token
I have voted No to this, and I hope I can convince some others to do the
same.
T_PAAMAYIM_NEKUDOTAYIM is such a famous token that there is probably
nobody in internals who doesn't know what it means, and for new
Hello internals,
As the two week discussion period has elapsed the vote is now open.
We did acknowledge the suggestion of dropping the token name from the error
message directly, but in our opinion this is an orthogonal change to the
one proposed, and has the risk of not landing in PHP 8.0.
The
12 matches
Mail list logo
