Hi, I didn't post this as a bug because I'm not sure whether this is done purposely or not. Say we have ClassB extending from ClassA. In Java, every constructor *must* call a super constructor – so either I can call one of the super constructors myself or leave it out, which will make the compiler automatically add a call to the default super constructor (visible, no-arg). If the super class doesn't have one, this will be a compile error.
Things are different in qooxdoo: If I don't call this.base(), the super constructor simply isn't invoked. Since there can only be one constructor function, the second part of the above won't apply either way, but not automatically calling the super constructor is definitely different behavior. Now – qooxdoo is not Java, so it's not necessarily a bug. But I did want to bring it up, just in case. Greetings -- View this message in context: http://qooxdoo.678.n2.nabble.com/Automatically-calling-super-constructor-tp7584460.html Sent from the qooxdoo mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Introducing Performance Central, a new site from SourceForge and AppDynamics. Performance Central is your source for news, insights, analysis and resources for efficient Application Performance Management. Visit us today! http://pubads.g.doubleclick.net/gampad/clk?id=48897511&iu=/4140/ostg.clktrk _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
