instanceof vs isPrototypeOf

[DHTML Kitchen]

When should I use instanceof vs isPrototypeOf() ?

function A(){}
function B(){}
function C(){}

B.prototype = new A();
C.prototype = new B();

var c = new C(); 
(c instanceof A); // true
A.prototype.isPrototypeOf( c ); // true
C.prototype.isPrototypeOf( c ); // true
(c instanceof C); // true

[MikeFoster]

Good question!

[DHTML Kitchen]

Am I overthinking this?

I'm just wondering if there is a reason to use one instead of another.

I can't think of any. (goto 0);

Maybe I need a break;

[SimplyFu]

is that javascript standards? I have never used it before

[MikeFoster]

@DHTML Kitchen:
I also tried to think of a situation where one would be more appropriate than the other... but I didn't come up with anything

@SimplyFu:
Yes, instanceof is an operator and was implemented in JavaScript 1.4. isPrototypeOf is a method of the Object object and "I think" it was implemented in JavaScript 1.5. That alone may be reason enough to use instanceof instead of isPrototypeOf.

[mrhoo]

If you want to find out if the object is an instance of Array, for example, it seems simpler to use instanceof than to see if it's prototype is the same prototype as the Array prototype.

I nearly always use if(obj.constructor==Array), because you can use obj.constructor to pass the constructor function, but for a simple test instanceof would be sufficient.

The only time I ever use isPrototypeOf is in debugging, when I need to track a method that is called or applied on a variety of custom objects.