Update article.md #1420
Update article.md #1420
Conversation
and -> or, methods -> methods I also have a question on the subject of this sentence (should this be a separate discussion entry?): In the "Extending built-in classes" article, in the "No static inheritance in built-ins" subsection, one finds: "But built-in classes are an exception. They don’t inherit statics from each other. For example, both Array and Date inherit from Object, so their instances have methods from Object.prototype. But Array.[[Prototype]] does not reference Object, so there’s no Array.keys() and Date.keys() static methods." In the "Extending built-in classes" article, in the "No static inheritance in built-ins" subsection, one finds: "But built-in classes are an exception. They don’t inherit statics from each other. For example, both Array and Date inherit from <code>Object</code>, so their instances have methods from <code>Object.prototype</code>. But <code>Array.[[Prototype]]</code> does not reference <code>Object</code>, so there’s no <code>Array.keys()</code> and <code>Date.keys()</code> static methods." This is a subject of some curiosity for me. Through a little testing, I believe I have found that, in fact <code>Array.[[Prototype]]</code> DOES, however, reference <code>Function.prototype</code>, i.e. <code>Array.__proto__ === Function.prototype</code> (<code>true</code>). (As does <code>Date.[[Prototype]]</code>). Is there someplace where this is explained? (Preferably in a way an intelligent 11-year-old could understand?).
|
The information about native prototypes is here: http://javascript.info/native-prototypes Should we cross-reference it maybe? |
|
I'm pretty familiar with that article. I meant somewhere where the connections I noted are explained -- why Array.proto === Function.prototype and Date.proto === Function.prototype. Makes it look like Function may be the internal constructor for Array and Date. I don't think that article covers that. |
|
That's simply because |
|
Yes, and Function and Object are also functions. Kind of brings to mind the old Country song "I am my own Grandpa". Also, Object, for instance, has methods of its own, while Function does not (except in Function.prototype). Personally, I'm getting a sense of it, but a bit more explanation in a skipable section could be nice. |
and -> or, methods -> methods
I also have a question on the subject of this sentence (should this be a separate discussion entry?):
In the "Extending built-in classes" article, in the "No static inheritance in built-ins" subsection, one finds:
"But built-in classes are an exception. They don’t inherit statics from each other.
For example, both Array and Date inherit from Object, so their instances have methods from Object.prototype. But Array.[[Prototype]] does not reference Object, so there’s no Array.keys() and Date.keys() static methods."
In the "Extending built-in classes" article, in the "No static inheritance in built-ins" subsection, one finds:
"But built-in classes are an exception. They don’t inherit statics from each other.
For example, both Array and Date inherit from
Object, so their instances have methods fromObject.prototype. ButArray.[[Prototype]]does not referenceObject, so there’s noArray.keys()andDate.keys()static methods."This is a subject of some curiosity for me. Through a little testing, I believe I have found that, in fact
Array.[[Prototype]]DOES, however, referenceFunction.prototype, i.e.Array.__proto__ === Function.prototype(true). (As doesDate.[[Prototype]]). Is there someplace where this is explained? (Preferably in a way an intelligent 11-year-old could understand?).