Hi Andreas, Am Saturday 06 November 2010 10:40:20 schrieb anzido GmbH: > (2) I think that the OXID developers wanted to prevent some classes from > beeing overloaded cause they are sort of basic for the whole shop > functionality and can easily screw the whole thing up. So I guess this had > been done to have some control about such essential stuff. But that's just > a guess ...
I don't think so. For this cases php knows keywords like 'final' or 'private'. Take a look to oxutilsobject::_makeSafeModuleClassParents( $aClassChain, $sBaseModule ) this method is declared as private. I think use the class chain (aModules) so early as possible is a good way. If some methods should be really protected you can do it with php keywords. Ok there exists ways to breakthrow private methods, but really a developer who know (and use) this, should know what he do. Regards, Markus _______________________________________________ dev-general mailing list [email protected] http://dir.gmane.org/gmane.comp.php.oxid.general
