Re: [PHP-DEV][RFC] Rename T_PAAMAYIM_NEKUDOTAYIM to T_DOUBLE_COLON

2020-06-10 Thread Walter Parker
On Wed, Jun 10, 2020 at 3:14 PM Sara Golemon wrote: > On Wed, Jun 10, 2020 at 3:33 PM Ryan Jentzsch > wrote: > > > OMG the trolling continues even today with this nonsense. Disappointing. > > > > Oh yes. And histrionics will certainly deescalate that issue. > > > > "...yes, it is broken, people

Re: [PHP-DEV][RFC] Rename T_PAAMAYIM_NEKUDOTAYIM to T_DOUBLE_COLON

2020-06-10 Thread Sara Golemon
On Wed, Jun 10, 2020 at 3:33 PM Ryan Jentzsch wrote: > OMG the trolling continues even today with this nonsense. Disappointing. > Oh yes. And histrionics will certainly deescalate that issue. > "...yes, it is broken, people have to Google or ask around for a very > unclear error message when

Re: [PHP-DEV][RFC] Rename T_PAAMAYIM_NEKUDOTAYIM to T_DOUBLE_COLON

2020-06-10 Thread Rowan Tommins
On 10/06/2020 19:28, Claude Pache wrote: One parsing error that I still find dreadful after more than 10 years of PHP coding, is: unexpected T_CONSTANT_ENCAPSED_STRING. Although T_CONSTANT_ENCAPSED_STRING is like Hebrew for me, I’ve learned with time that when I get such an error, it means

Re: [PHP-DEV][RFC] Rename T_PAAMAYIM_NEKUDOTAYIM to T_DOUBLE_COLON

2020-06-10 Thread Chase Peeler
On Wed, Jun 10, 2020 at 4:33 PM Ryan Jentzsch wrote: > OMG the trolling continues even today with this nonsense. Disappointing. > Calling T_PAAMAYIM_NEKUDOTAYIM a non-issue is simply wrong and here's why:: > "People don’t ask for the other parse errors even half as often as they as > for

Re: [PHP-DEV][RFC] Rename T_PAAMAYIM_NEKUDOTAYIM to T_DOUBLE_COLON

2020-06-10 Thread Ryan Jentzsch
OMG the trolling continues even today with this nonsense. Disappointing. Calling T_PAAMAYIM_NEKUDOTAYIM a non-issue is simply wrong and here's why:: "People don’t ask for the other parse errors even half as often as they as for T_PAAMAYIM_NEKUDOTAYIM They do so because it looks like gibberish to

[PHP-DEV] 8.0 release dates

2020-06-10 Thread Sara Golemon
TL;DR - Good news everyone! You have an extra week before feature freeze, and GA is coming earlier than expected! As alpha1 approaches, I was reviewing the scheduled release dates for 8.0 and noticed that we were offset from the active branch releases by 1 week. In the interest of keeping

Re: [PHP-DEV][RFC] Rename T_PAAMAYIM_NEKUDOTAYIM to T_DOUBLE_COLON

2020-06-10 Thread Claude Pache
Hi, I appreciate the effort to reduce frustration in PHP coding. However, T_PAAMAYIM_NEKUDOTAYIM is a non-issue: you learn it once and you’re done for the rest of your life. May I suggest an improvement that would be much more useful than renaming tokens? One parsing error that I still find

Re: [PHP-DEV][RFC] Rename T_PAAMAYIM_NEKUDOTAYIM to T_DOUBLE_COLON

2020-06-10 Thread Chuck Adams
(Trying again without a plussed address, which is too much hassle for the ML. Sorry for dups.) Honestly, I'd rather PHP didn't barf raw lex tokens to the end user for its output. But until then, renaming it seems wise. Didn't someone come out and claim that the current token is misspelled

Re: [PHP-DEV][RFC] Rename T_PAAMAYIM_NEKUDOTAYIM to T_DOUBLE_COLON

2020-06-10 Thread Chase Peeler
Encountering T_PAAMAYIM_NEKUDOTAYIM is a right of passage in the PHP world. I had to deal with it, so should everyone else. :-P While it'll be bittersweet to see it go, I definitely think this would be a wise update. On Wed, Jun 10, 2020 at 12:58 PM Ryan Jentzsch wrote: > With over 25+ years

Re: [PHP-DEV][RFC] Rename T_PAAMAYIM_NEKUDOTAYIM to T_DOUBLE_COLON

2020-06-10 Thread Ryan Jentzsch
With over 25+ years of software development experience it was In 2016 I was introduced to the world of PHP development. One day I came across the most unusual of error messages "T_PAAMAYIM_NEKUDOTAYIM" What the hell is this?!? That I needed to waste my time to Google this is simply insane. At the

Re: [PHP-DEV] RFC: separate inheritance from subtyping (PHP v8)

2020-06-10 Thread Larry Garfield
On Wed, Jun 10, 2020, at 11:16 AM, Doug Wilbourne wrote: > I propose the following language additions: > > > > 1) add three new keywords to the available syntax for class declarations: > 'inherits' and 'subtypes' and 'patterns'. > > > > Currently the 'extends' keyword means both inherits and

[PHP-DEV] RFC: separate inheritance from subtyping (PHP v8)

2020-06-10 Thread Doug Wilbourne
I propose the following language additions: 1) add three new keywords to the available syntax for class declarations: 'inherits' and 'subtypes' and 'patterns'. Currently the 'extends' keyword means both inherits and subtypes, which leads to unnecessarily restrictive typing problems in order

Re: [PHP-DEV] [RFC] Shorter attribute syntax

2020-06-10 Thread Theodore Brown
On Wed, June 10, 2020 at 3:11 AM Michał Brzuchalski wrote: > I just noticed a power of Rusts outer attributes which this syntax > count follow in a future. Following outer attributes in Rust's we > could introduce in a future syntax like > >

[PHP-DEV][RFC] Rename T_PAAMAYIM_NEKUDOTAYIM to T_DOUBLE_COLON

2020-06-10 Thread G. P. B.
Greetings PHP internals, Kalle Sommer Nielsen and myself are proposing to rename the T_PAAMAYIM_NEKUDOTAYIM token into the already existing T_DOUBLE_COLON alias, T_PAAMAYIM_NEKUDOTAYIM would then become an alias to T_DOUBLE_COLON. The RFC is located here:

Re: [PHP-DEV] [RFC] Shorter attribute syntax

2020-06-10 Thread Theodore Brown
Hi Sebastian, On Wed, June 10, 2020 at 12:37 AM Sebastian Bergmann wrote: > Am 09.06.2020 um 17:57 schrieb Theodore Brown: > > That's an interesting argument. After thinking about it more, though, > > I'm not sure I understand what the benefit would be. The docblock > > annotation needed for

Re: [PHP-DEV] [RFC] Shorter attribute syntax

2020-06-10 Thread Michał Brzuchalski
wt., 9 cze 2020 o 13:56 Benjamin Eberlei napisał(a): > On Thu, Jun 4, 2020 at 1:55 AM Theodore Brown > wrote: > > > Hi internals, > > > > I discussed the syntax for attributes further with Benjamin, Martin, > > and several other internals developers off-list, and with their > > feedback