Re: BC break in 7.2 caused by undocumented and unauthorised change
| From: | Tony Marston | Date: | Fri, 25 May 2018 08:59:56 +0000 |
| Subject: | Re: BC break in 7.2 caused by undocumented and unauthorised change | ||
| References: | 1 2 3 4 5 6 7 | Groups: | php.general |
| Request: | Send a blank email to php-general+get-326483@lists.php.net to get a copy of this message | ||
"Paul M Foster" wrote in message news:20180524155517.GI26444@quillandmouse.com...
On Thu, May 24, 2018 at 03:01:18PM +0100, tony@marston-home.demon.co.uk wrote: [snip]Ignoring the reasons for me being banned, what do you think of the idea that a BC break can be snuck into the language WITHOUT prior warning, WITHOUT being discussed in the internals list and WITHOUT being voted upon, and WITHOUT any changes in the documentation? *THAT* is the real issue here. If this is allowed to become standard practice then I'm afraid that the PHP language will become so unreliable that it will be effectively unusable. -- Tony MarstonThat just proves that the age old notion of free speech does not exist on the internals list.I'm not involved in any of the current drama and I have no skin in this game. But I do get tired of people who are called out for bad behavior consistently claiming that some supposed right to free speech they think they have has been trampled. Indeed, you do have an a priori right to speak freely. But that "right" may be curtailed relative to the venue involved. Realize that in order to speak as freely as you like, you may have to devise your own platform from which to speak. Because people in their own venues don't owe you the time of day when it comes to "free speech".