Re: [RFC] Remove PHP 4 Constructors

On Wed, Jan 21, 2015 at 9:50 AM, Tony Marston <TonyMarston@hotmail.com> wrote: > > You are totally missing the point. It is the principle of having to spent > unknown quantities of time in refactoring my code for nothing more than a > frivolous and unnecessary break in BC. It does not fi a bug or a security > issue, therefore it is frivolous and unnecessary > > Yet you seem to have no problem wasting loads of time arguing about it on the internet. > You cannot remove anything from the language until after it has been > marked a deprecated, and the simple fact is that PHP 4 constructors have > NEVER been marked as deprecated. I have used every PHP 5 release up to and > including the latest (5.6..4) with error_reporting set to E_ALL and all my > code has run without producing any error messages. I don't even know what you're responding to here; I didn't suggest removing it from the language, nor that it was deprecated. I suggested updating the manual to discourage use. This is a baby step toward actual deprecation. 1) discourage use of it on the website, 2) provide deprecation notices in a future version of PHP, 3) sometime in the distant future, actually remove it. On Wed, Jan 21, 2015 at 9:50 AM, Tony Marston <TonyMarston@hotmail.com> wrote: > "Kristopher" wrote in message > news:CAF9U7z-bkYRDwAL8CA4_= > 1DhOrL0evP_MZWF6QWQScwDf7NpAA@mail.gmail.com... > >> >> On Tue, Jan 20, 2015 at 8:26 AM, Tony Marston <TonyMarston@hotmail.com> >> wrote: >> >> @tony: What's really interesting is that all this time you've spent >> arguing >> could have been used to update your code and make this no longer an issue >> for you. >> > > You are totally missing the point. It is the principle of having to spent > unknown quantities of time in refactoring my code for nothing more than a > frivolous and unnecessary break in BC. It does not fi a bug or a security > issue, therefore it is frivolous and unnecessary > > >> @everyone: Would an RFC be necessary to update the PHP manual to actually >> recommend the PHP 5 constructors and recommend against using the PHP 4 >> style constructors, using very explicit language? If not, should this >> change be made, regardless of the outcome of the RFC to remove PHP 4 >> constructors? >> > > You cannot remove anything from the language until after it has been > marked a deprecated, and the simple fact is that PHP 4 constructors have > NEVER been marked as deprecated. I have used every PHP 5 release up to and > including the latest (5.6..4) with error_reporting set to E_ALL and all my > code has run without producing any error messages. > > -- > Tony Marston > > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > >