>> BTW there is a small problem in your code: >> /* current call-stack */ >> __recursionInfo: *new* Array(), // <-- this array will be shared
As a poor defense I could argue that after one run the array is empty again and JS is not multithreaded so far ;-) Anyway thanks for this hint - I remember having read about this in the docs somewhere else but when it comes to programming such things are very easy to forget. When thinking about it ... wouldn't it make sense to extend Class.define to issue warnings in the log if references on members are filled before calling the constructor ? Since the way I wrote it is very common in every other object-oriented language, but due to JS-limitations behaves totally different in qooxdoo I think it would make sense to enforce constructor initialization of members. Actually 'early'-initializing references makes only sense on statics ? ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ qooxdoo-devel mailing list qooxdoo-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
