Re: [alexander.schrijver@gmail.com: Re: [PHP-DEV] RE: [SPAM] Re: [PHP-DEV] rename T_PAAMAYIM_NEKUDOTAYIM to T_DOUBLE_COLON]
| From: | Etienne Kneuss | Date: | Mon, 01 Nov 2010 12:36:24 +0000 |
| Subject: | Re: [alexander.schrijver@gmail.com: Re: [PHP-DEV] RE: [SPAM] Re: [PHP-DEV] rename T_PAAMAYIM_NEKUDOTAYIM to T_DOUBLE_COLON] | ||
| References: | 1 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-50053@lists.php.net to get a copy of this message | ||
On Nov 01 13:30:58, Alexander Schrijver wrote:
> Oops, should've sent this to the list too.
>
> ----- Forwarded message from Alexander Schrijver <alexander.schrijver@gmail.com> -----
>
> Date: Mon, 1 Nov 2010 13:28:59 +0100
> From: Alexander Schrijver <alexander.schrijver@gmail.com>
> To: James Butler <james.butler@edigitalresearch.com>
> Subject: Re: [PHP-DEV] RE: [SPAM] Re: [PHP-DEV] rename T_PAAMAYIM_NEKUDOTAYIM to
> T_DOUBLE_COLON
> User-Agent: Mutt/1.5.21 (2010-09-15)
>
> On Mon, Nov 01, 2010 at 12:23:07PM +0000, James Butler wrote:
> >
> >
> > -----Original Message-----
> > From: Alexander Schrijver [mailto:alexander.schrijver@gmail.com]
> > Sent: 01 November 2010 12:19
> > To: Stefan Marr
> > Cc: Dennis Haarbrink; Stan Vass; internals@lists.php.net
> > Subject: Re: [PHP-DEV] RE: [SPAM] Re: [PHP-DEV] rename T_PAAMAYIM_NEKUDOTAYIM to
> > T_DOUBLE_COLON
> >
> > On Mon, Nov 01, 2010 at 12:59:54PM +0100, Stefan Marr wrote:
> > >
> > > On 01 Nov 2010, at 12:06, Alexander Schrijver wrote:
> > > > Its a minor change and an annoyance to a lot of people. Yes, by not changing
> > > > this you'r annoying thousands of people.
> > > Instead of going for this cosmetic nonsense you should help those people on the lemon
> > > branch.
> > > I am insulted every time I have to read a parser token name in an error message,
> > > instead of a sensible error message.
> > > The cost of understanding T_PAAMAYIM_NEKUDOTAYIM as part of the current mumbo-jumbo
> > > is completely insignificant compared to the cost of actually understanding the error message just
> > > indicating what the parser would have expected.
> > >
> > > Changing to lemon is the only way to actually achieve something in the long run...
> >
> > Right, and be forced to introduce some bullshit hebrew when its done. No, thank you.
> >
> > Err, the entire point is that it won't matter what the underlying token is. The error
> > as seen can be anything you want it to be, or at least you can have a fight about what the new
> > message looks like and i'm sure there won't really be a compelling reason for it to be in
> > hebrew (unless localized).
> > Please grow up...
>
>
> It's the policy:
> > There are two reasons this term will stay. It is a tip of the hat to
> > the amount of PHP work that came out of Israel, and it is a good
> >
> > reminder that there are a lot of other languages in the world. People
> > whose first language is not English, myself included, are forced to work
> > with unfamiliar terms every day. I wouldn't mind having a few more
> >
> > non-English identifiers in PHP actually.
> >
> >
> >
> > Well, and a third reason, I like it.
>
> There is some reason this policy will change after i write this new tokenizer?
Yes, there is a reason:
As it was explained before, lemon would not display token names but
actual token "values". So instead of "Unexpected T_PAABLAH" it would say
"Unexpected '::' ..."
Best,
>
>
> ----- End forwarded message -----
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
--
Etienne Kneuss
http://www.colder.ch