Can you explain to me how that's better than either fixing at Engine
level or recommending display_startup_errors is switched off?
Because PHP does not have any way to do this (java):
((ParentClass)object)->methodThatIsOverWrittenInSubClass();
the only way to do this in php is via Reflection, which is very, very
unconvenient.
This is the FIRST TIME you have even mentioned Reflection. So would you care to tell us what the real problem is, from where you're standing? Evidently it's nothing to do with the E_STRICT, which is only thrown if you turn on something in php.ini that is off by default.
Further, while making the changes, I saw that the things that the
methods do are really different.
You shouldn't have been making any changes at this point, sorry but.
So if a subclass overwrites a method
defined in an ancestor class, you have nearly no way to get that parent
method functionality back. While methods with the same signature most
likely do the same things and sometimes even call the parent, this is
not true for methods with different signatures.
Right, this is what we (Dmitry, Andrei, me) were talking about.
Thus renaming them is the only way to make the functionality accessible
for the user at all.
Unless that behaviour changes in PHP.
And please don't take unilateral decisions without discussion.
I thought the discussion was open for some months. And Andrei seemed to
have the same opinion.
Andrei's last post on the matter was a question inviting discussion. If you've been discussing this with him off-list at least have the courtesy to share the decision before (or even while) you implement it. If you haven't - there was no discussion.
- Steph
-- Regards/MfG,
Christian Weiske