Ok, just checked the mailing list (and sorry for top-posting)

July 31st.  RFC announced
Jul 31st - 6 or 7 mails  at least one very negative, a couple for it.
August 1,3,5,6 - 5 or 6 emails getting a bit off-topic.
Jan 21st - call to vote (single email - no-one replied on list)... - got 15 +1 votes
Jan 28th - announced success..

I know it's not deliberate, but it looks like this change is just a BC disaster waiting to happen, anyone who has been using PHP for more that a few years, before traits, knows this is how to simulate multiple inheritance, it's basically textbook PHP for some of us old boys.. ;)

It looks like the justification in the RFC is basically it's a WTF for beginners. Sorry, but this is pretty identical to javascript behavior (which does take some understanding, but is very powerful), so there is no WTF, or surprise, once you seen it done, and understand it..

If you where suggesting that calling a non-static method from global scope would cause some kind of E_DEPRECIATED, I'd agree, it's a good idea. but I'm not convinced that this proposal is particularly well thought through.

Ok, that's all for tonight ;)

Regards
Alan



On Monday, January 28, 2013 11:01 PM, Gustavo Lopes wrote:
On Mon, 28 Jan 2013 15:49:26 +0100, Alan Knowles <a...@roojs.com> wrote:

I was trying to vote against, for what it's worth.

It's a major bc break with no obvious value, and what appears to be 7 days given to vote when every one is busy discussing a new property syntax.

Traits is cute, but this was a amazing feature of the PHP language, not obvious, but it's pretty similar to Javascript, not sure why it would be so confusing.....

Sorry for being contrary, but i was a but shocked that this was.going to be removed


You had more than 6 months to voice your concerns. There was a discussion when the feature was proposed during summer. I'm sorry you did not notice it, but I can't be spamming the list every once in a while to maximize the number of people that are aware of what's going on.

Concerns about voting periods not having an upper bound notwithstanding, there was nothing remotely irregular about the way the process was conducted. I therefore find your comments about "sneaking this in" rather odd. Blame yourself instead.

Again, I'm not commenting on the merits.



--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php

Reply via email to