Hi Til, You were right, I meant this.superclass and also it is dangerous.
The Dojo approach for managing inheritance seems smarter: http://manual.dojotoolkit.org/WikiHome/DojoDotBook/Book20 They provide the "this.inherited" mechanism for this purpose. Til Schneider schrieb: >>>> proto.func = function() { >>>> // How can I call here BaseClass.func()? >>>> return 'In derived class'; >>>> } >>>> >>>> >>> BaseClass.func.call(this, param1, param2); >>> > > >> Or even better: >> >> proto.func = function() { >> superclass.func.call(this); >> return 'In derived class'; >> >> } >> > > I think you mean: > this.superclass.func.call(this); > > But this is dangerous, because if you create another subclass of > DerivedClass, then this.superclass will contain DerivedClass and not > BaseClass any more. Then you will get an endless loop. > > > > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share your > opinions on IT & business topics through brief surveys -- and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > qooxdoo-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel > > ______________________________________________ LLama Gratis a cualquier PC del Mundo. Llamadas a fijos y móviles desde 1 céntimo por minuto. http://es.voice.yahoo.com ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
