Re: [SPAM] Re: [PHP-GTK-DEV] E_STRICT renamings
| From: | Christian Weiske | Date: | Sat, 02 Sep 2006 11:58:10 +0000 |
| Subject: | Re: [SPAM] Re: [PHP-GTK-DEV] E_STRICT renamings | ||
| References: | 1 2 3 4 5 6 | Groups: | php.gtk.dev |
| Request: | Send a blank email to php-gtk-dev+get-3373@lists.php.net to get a copy of this message | ||
Steph,
> 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.
Further, while making the changes, I saw that the things that the
methods do are really different. 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.
Thus renaming them is the only way to make the functionality accessible
for the user at all.
> 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.
--
Regards/MfG,
Christian Weiske