CODEWITHSUNDEEP
javascriptprototype
Duncan
Duncan

Reputation: 1213

Null prototype, Object.prototype and Object.create

Why is it that setting the prototype property of a constructor function to null does not prevent objects created from that function from calling through to methods on Object.prototype, in the same way that setting the prototype to Object.create(null) does?

That is, why is this the case:

function Foo(){}
Foo.prototype = null;
console.log(new Foo().toString); //outputs function toString() { [native code] } (or whatever)

function Foo(){}
Foo.prototype = Object.create(null);
console.log(new Foo().toString); //output undefined

Upvotes: 15

Views: 17315

Answers (1)

Benjamin Gruenbaum
Benjamin Gruenbaum

Reputation: 276296

In short

Yes, your observation is correct - a function constructed with the new operator will always have an object prototype in this case Object.prototype and this is indeed unlike a function created with Object.create.

On why

One can see this behavior completely specified in the ES5 language specification on which JavaScript is based on. Let's see this.

In new:

Quoting the specification of the [[Construct]] method of functions that indicates how object creation using the new operator is performed we can see that the following is specified:

If Type(proto) is not Object, set the [[Prototype]] internal property of obj to the standard built-in Object prototype object as described in 15.2.4.

In Object.create:

On the other hand, if we check out The spec for Object.create we can see that Object.create(o) specifies:

Set the [[Prototype]] internal property of obj to O.

Which means we can set it, it also explicitly checks that it is null or Object in that algorithm (please do follow the link to the spec and read it :))

So the prototype of the objects called with new Foo is Object.prototype and not null. It is impossible to create objects with no prototype without Object.create using standard methods only.

Upvotes: 34

Related Questions