Yes, If they try to upgrade to the new release.
No, because their applications will more that likely stop working because of a BC break.
They are still running older versions of PHP simply because their customers’ applications won’t run on the latest release due to all those BC breaks.
PHP 4 constructors are still fully supported in PHP simply because they have NEVER been marked as deprecated, so to say that they are obsolete and should not be used is just plain WRONG!
[quote=“mAAdhaTTah, post:40, topic:110202”]
and if the current method of using them can cause conflicts, [/quote]
The only “conflict” that has been reported is where a newbie programmer creates a class method with the same name as the class, and without a separate __construct() method, without realising that it automatically becomes the constructor instead of a separate callable method. Such newbie developers should RTFM (Read The Friggin’ Manual).
The downside is all the unnecessary refactoring that developers have to go through in order to upgrade to a new release because of a frivolous BC break. I use the term “frivolous” because it is not to solve a genuine bug or security issue.