The statics thing doesn't bother me enough to introduce this "workaround",
thanks though! I'll just write my hashCode method myself such that it just
considers all properties in the object – objects equal by a certain equals()
method will then have the same hashCode. The opposite won't be true, but
isn't required in the hashCode contract.

As for the anonymous classes thing I'll just give it a try. Thanks so far!



--
View this message in context: 
http://qooxdoo.678.n2.nabble.com/Several-questions-abstract-classes-static-methods-hashcode-tp7584329p7584334.html
Sent from the qooxdoo mailing list archive at Nabble.com.

------------------------------------------------------------------------------
Get 100% visibility into Java/.NET code with AppDynamics Lite!
It's a free troubleshooting tool designed for production.
Get down to code-level detail for bottlenecks, with <2% overhead. 
Download for free and get started troubleshooting in minutes. 
http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel

Reply via email to