I remember error messages have been improved since last decade, but
they were engine ones.
Parser ones have never been touched, so to improve them, I +1 your
idea Felipe :)
Julien
On Mon, May 16, 2011 at 7:52 PM, Florian Anderiasch wrote:
> On 16.05.2011 14:15, Felipe Pena wrote:
>> Other exampl
On 16.05.2011 14:15, Felipe Pena wrote:
> Other examples and patch at:
> https://wiki.php.net/rfc/improved-parser-error-message
Just for completeness, here's the lengthy thread
we had in October 2010 about this:
http://news.php.net/php.internals/49978
FWIW, I like the Easter Egg :)
Greetings,
F
+1
Regards
Pierrick
On 16 May 2011 08:15, Felipe Pena wrote:
> Hi all,
> As I have proposed previously in an old thread... What about we name all
> the
> tokens to have an improved parser error message? (i.e. anymore
> T_PAAMAYIM_NEKUDOTAYIM, T_DOLLAR_OPEN_CURLY_BRACES in the messages etc)
>
>
Hi Felipe,
On May 16 9:15:24, Felipe Pena wrote:
> Hi all,
> As I have proposed previously in an old thread... What about we name all the
> tokens to have an improved parser error message? (i.e. anymore
> T_PAAMAYIM_NEKUDOTAYIM, T_DOLLAR_OPEN_CURLY_BRACES in the messages etc)
>
> Some examples:
Hi,
2011/5/16 Ferenc Kovacs
>
> +1
>
> do you think that this could cause some kind of BC?
> I don't think that anybody out there parses the tokens as is, but there are
> crazy people. :)
> the other thing that I can imagine that the developers will be surprised
> that they are getting meaningfu
On Mon, May 16, 2011 at 2:15 PM, Felipe Pena wrote:
> Hi all,
> As I have proposed previously in an old thread... What about we name all
> the
> tokens to have an improved parser error message? (i.e. anymore
> T_PAAMAYIM_NEKUDOTAYIM, T_DOLLAR_OPEN_CURLY_BRACES in the messages etc)
>
> Some exampl
