by Dmitry Soshnikov
Read this article in: Russian, Chinese (version 1, version 2).
As we already know from the second chapter concerning the variable object, the data of an execution context (variables, function declarations, and formal parameters of functions) are stored as properties of the variables object.
Read more »
Read this article in: Russian, Chinese (version1, version2, version 3).
Always in programs we declare functions and variables which then successfully use building our systems. But how and where the interpreter finds our data (functions, variable)? What occurs, when we reference to needed objects?
Read more »
Read this article in: Russian, Chinese (version1, version2, version 3).
In this article we will discuss one more detail directly related with execution contexts. The topic of discussion is the this keyword.
Read more »
Read this article in: Russian.
This is the second part of article about object-oriented programming in ECMAScript. In the first part we discussed the general theory and drew parallels with ECMAScript. Before reading of the current part, if it is necessary, I recommend reading the first part as in this article we will actively use the passed terminology. You can find the first part here: ECMA-262-3 in detail. Chapter 7.1. OOP: The general theory.
Read more »
Read this article in: Russian.
In this article we consider major aspects of object-oriented programming in ECMAScript. That the article has not turned to “yet another” (as this topic already discussed in many articles), more attention will be given, besides, to theoretical aspects to see these processes from within. In particular, we will consider algorithms of objects creation, see how relationships between objects (including the basic relationship — inheritance) are made, and also give accurate definitions which can be used in discussions (that I hope will dispel some terminological and ideological doubts and messes arising often in articles on OOP in JavaScript).
Read more »
Read this article in: Russian, Chinese.
In this article we will talk about one of the most discussed topics related with JavaScript — about closures. The topic, as a matter of fact, is not new and was discussed many times. However we will try to discuss and understand it more from theoretical point of view, and also will look at how closures are made in ECMAScript from within.
Read more »
Recently some JavaScript quizzes appear then and there with the competitive titles wondering whether “you know JavaScript”? The recent quizzes were by kangax, Dmitry Baranovskiy and by Nicholas C. Zakas. All that quizzes are interesting, many questions though are mostly theoretical rather than practical.
And again just for fun, I suggest another ECMAScript quiz. I won’t use some boring things such as “a+++b”; but I will more sophisticated 
Some interesting questions are collected from newsgroups, mailing lists, forums and from my own.
Read this article in: English.
В этой небольшой заметке мы рассмотрим стратегии передачи параметров в функции в ECMAScript.
В общем случае данный раздел компьютерной науки называется стратегия оценки, вычисления (evaluation strategy), т.е. свод правил для оценки и определения какого-либо выражения. Стратегия передачи параметров в функцию, является её частным случаем.
Read more »
Read this article in: English.
Данная статья является продолжением статьи об объектно-ориентированном программировании в ECMAScript. В первой части мы разбирали общую теорию и проводили параллели с ECMAScript. Перед прочтением текущей части, если есть необходимость, я рекомендую прочесть первую часть, поскольку в этой статьей мы будет активно опираться на пройденную терминологию. Желающие могут найти первую часть здесь: Тонкости ECMA-262-3. Часть 7.1. ООП: Общая теория.
Read more »
maksimr on Тонкости ECMA-262-3. Часть 3. This.@max Если вы говорите про этот пример: [js]var foo = { bar: function () { alert(this); } }; (false ||...
max on Тонкости ECMA-262-3. Часть 3. This.в примере "Вызов функции и НЕ тип Reference" команда (false || foo.bar)(); возрашает true 
Dmitry Soshnikov on ECMA-262-3 in detail. Chapter 3. This.@Shawn I see correct output in your example. I guess output format of the consoles may confuse, but: foo.bar(); correctly...