http://www.projectcss.net/oop-test/2/

As I said above I’ve been using this for a while with no problems, the reason being, I don’t use parent method calling all that often lol Makes me wonder how useful it actually is? I mean, if parent methods aren’t being called all the time, then it only takes a second to type an explicit call.

@WebReflection – I’m not sure what you mean by “unreasonably fast”? In the context is that an oxymoron? lol

“the trick over toString is not elegant and could fail with the first library that override toString function”

My class implementation is totally modular, relying on standalone OO methods to do the work, so if somebody wanted a more thorough function for copying over methods they can feel free to swap out the one provided. I haven’t run in to any problems with the current implementation and I’ve been using it for a while. I like to keep things as complicated as necessary :o)

“Maybe we could combine both solutions to find the fastest trick maintaining code elegance, can we?”

Not sure if that was aimed at me, but feel free to drop me an email. My address is my username – @hotmail.co.uk

Thanks

function WR_Level0() { }
function WR_Level1() { this.parent(); }
wr.extend(WR_Level1, WR_Level0, { });
function WR_Level2() { this.parent(); }
wr.extend(WR_Level2, WR_Level1, { });
var Obj = new WR_Level2(); // too much recursion

I liked your article, however, using John Resig’s Class is a bit unfair. It doesn’t do half the stuff that mootools and prototype do and it’s broken/not complete. In IE it will break if you use a method name that mirrors those with the DontEnum attribute (mootools has the same error). Also it doesn’t return the correct constructor. Both simple fixes, but I bet folk grab that code as it appears to be the fastest and then will run in to problems.

I’ve uploaded another test similar to yours that also tests for the above problems, letting you know if they “Passed” or “Failed”. I’ve also included in the tests my own Class implementation which I’ve been using for a while now and it seems to perform the best, this is due to the way I do parent method calling.

http://www.projectcss.net/oop-test/

Note, too, that object instantiation is typically a relatively infrequent operation compared to method invocation. In most cases a performance hit of incurred when creating an object will be much less than the hit you take in subsequent method calls on the object.

What are you referring to with the “shouldn’t try to mimic classes” line?

I use MooTools, and since I started writing code in the class format they offer that is typical in other languages, my code is waaay more portable, very DRY, reusable, extensible, and clean. That is the biggest win I got from using the framework thus far. Classes used in this way give you an edge in my opinion.

Note: I’m not saying JSLitmus provides 100% accurate results, btw. Results will be affected by the browser doing garbage collection, by other apps taking CPU time, and even by OSes that vary CPU speed in response to app demand (typically only seen on laptops.) But I haven’t seen the particular issue you’re referring to.