ECMA-262-3. Chapter 7. OOP.

[Dmitry A. Soshnikov]

Another one part of my articles is translated. "This is Chapter 7.
OOP". There are two parts. All interested can find it there (all not
interested or those who show that they are not interested are also
welcome ):

"ECMA-262-3 in detail. Chapter 7.1. OOP: The general theory."

<URL: http://dmitrysoshnikov.com/ecmascript/chapter-7-1-oop-general-theory/>

"ECMA-262-3 in detail. Chapter 7.2. OOP: ECMAScript implementation."

<URL: http://dmitrysoshnikov.com/ecmascript/chapter-7-2-oop-ecmascript-implementation/>

Again, I'll be glad for any wording mistakes corrections. Although
kangax helped to correct some small wording mistakes in first part, I
suppose there are still some wording mistakes in both parts. Technical
corrections and additions are also of course acceptable.

This chapter (as actually all this articles) is mostly about theory,
so interested in ES deeply will find it interesting.

Dmitry.

 

[John G Harris]

Another one part of my articles is translated. "This is Chapter 7.
OOP". There are two parts. All interested can find it there (all not
interested or those who show that they are not interested are also
welcome ):

"ECMA-262-3 in detail. Chapter 7.1. OOP: The general theory."

<URL: http://dmitrysoshnikov.com/ecmascript/chapter-7-1-oop-general-theory/>

<snip>

1
I'm not sure what you mean by 'moment' but in most places I'm sure you
don't mean a moment in time.

Did you mean 'idea', 'thought', 'principle', 'concept'? Using 'concept'
would be best, but it's been misused too often.

2
In the "General Provisions" section, "Prototype based model of OOP"
should be "ECMAScript based model of OOP". Traditional prototype-based
languages aren't like ECMAScript.

John

 

[Dmitry A. Soshnikov]

  <snip>

1
I'm not sure what you mean by 'moment' but in most places I'm sure you
don't mean a moment in time.

Did you mean 'idea', 'thought', 'principle', 'concept'? Using 'concept'
would be best, but it's been misused too often.

Thanks, yeah I meant "features", "aspects" - the "key feature" - in
meaning - "the major features", maybe, "the main/general/ features".
Which word to choose better? Also there's "moment" in meaning the
moment of time.

2
In the "General Provisions" section, "Prototype based model of OOP"
should be "ECMAScript based model of OOP". Traditional prototype-based
languages aren't like ECMAScript.

What exactly do you mean? First part of this chapter mostly devoted to
general theory with describing prototype-based model in general - with
two kinds: delegation based prototyping which is used in ECMAScript
and concatenative prototyping - just to mention that such kind of
prototyping also is. As examples I use pseudo-code with describing
delegation-based prototyping. What kind of (traditional) prototyping
do you mean?

And about ECMAScript OOP implementation - that's completely in part 2
of this chapter.

Dmitry.

 

[Dmitry A. Soshnikov]

[...]

Did you mean 'idea', 'thought', 'principle', 'concept'? Using 'concept'
would be best, but it's been misused too often.

Thanks, yeah I meant "features", "aspects" - the "key feature" - in
meaning - "the major features", maybe, "the main/general/ features".
Which word to choose better?

Sorry, didn't notice that you already suggested word "concept". Yeah,
I'll use it with combination with word "feature" (as there're many
places where this word should be used). Is it OK with "feature" as a
synonym?

Dmitry.

 

[Dmitry A. Soshnikov]

[...]

1
I'm not sure what you mean by 'moment' but in most places I'm sure you
don't mean a moment in time.

Did you mean 'idea', 'thought', 'principle', 'concept'? Using 'concept'
would be best, but it's been misused too often.

Thanks, updated to variations of "concept", "feature" and
"case" (where was "in this moment there is a mess" => "in this case
there is ...").

Dmitry.

 

[John G Harris]

What exactly do you mean? First part of this chapter mostly devoted to
general theory with describing prototype-based model in general - with
two kinds: delegation based prototyping which is used in ECMAScript
and concatenative prototyping - just to mention that such kind of
prototyping also is. As examples I use pseudo-code with describing
delegation-based prototyping. What kind of (traditional) prototyping
do you mean?

To me a traditional prototype based language is one where new objects
are created by cloning another object. The object cloned from is the
'prototype' of that kind of object. The author of the Wikipedia article
on prototype based languages thinks the same.

This isn't how it works in ECMAScript where cloning is not very easy.

John

 

[Dmitry A. Soshnikov]

To me a traditional prototype based language is one where new objects
are created by cloning another object. The object cloned from is the
'prototype' of that kind of object. The author of the Wikipedia article
on prototype based languages thinks the same.

This isn't how it works in ECMAScript where cloning is not very easy.

Yes, that's right. But that's not about author from Wikipedia, it's
about the general theory. And both kinds of prototyping I mentioned:

(a) concatenative - when a prototype object is a original copy from
which other objects are cloned;

(b) delegation based - when a prototype object is an object to which
properties delegate other objects in case of absence such own
properties.

But the title "ECMAScript based model of OOP" doesn't fit, because
that ECMAScript which uses delegation based model (and it was invented
before the ECMAScript) but not vice versa. So the section is named
generally "Prototype based ..." in which concatenative and delegation
based models considerate.

Dmitry.