The PHP 7 Revolution: Return Types and Removed Artifacts

[mAAdhaTTah]

@TomB

Let’s also keep in mind here that the set of users who will be affected are the ones who:

a) Use PHP4 constructors
and
B) Want to upgrade to PHP7

I think this is going to be the most important part. I’m really inclined to doubt this is a significant number of people.

@tony_marston404

Are you aware of how many PEAR components were written for PHP 4 and have never been updated to use PHP 5 constructors?

Is anyone still using PEAR? PHPUnit just deprecated its PEAR install, and I’d much rather use Composer than PEAR for basically anything.

Edit: Let me rephrase: is anyone who is going to upgrade to PHP7 still using PEAR?

Anyone who’s starting a new project is not using PHP4 constructors. Anyone who’s got a legacy project isn’t going to upgrade to PHP7. I really fail to see what the issue is.

@tony_marston404

I certainly would not be in favour in creating any new inconsistencies, but I am not in favour of breaking the language to remove minor inconsistencies that have existed for decades and which do not cause problems for most developers.

I would suggest removing PHP4 constructors isn’t going to cause problems for most developers.