The PHP 7 Revolution: Return Types and Removed Artifacts

[swader]

@tony_marston404

BTW, the name is Tony with a “y”, not Toni with an “i”

My apologies, I have no idea how that got past me. I know many males with the name “Toni”, so it never seemed out of the ordinary. I have updated the post.

@tony_marston404

There is a rule that nothing can be removed from the language without it being marked as deprecated first, and PHP 4 constructors have never been marked as deprecated. As the next major release as 5.6 will be 7 (the need for 5.7 was voted down) it will therefore not be possible to remove them in 7.

I agree, this should have been addressed by either not removing the functionality, or by marking it as deprecated first. Jumping to removals is not healthy for the language’s ecosystem.

@tony_marston404

The idea that the core developers can remove long-standing functionality from the language FOR NO GOOD REASON

But they, the makers of the language, believe they have a good reason. Who is to argue which reason is good and which isn’t? The majority? In this particular instance, I objectively believe you are the minority.