Re: es-discuss Digest, Vol 52, Issue 117

2011-06-21 Thread Mariusz Nowak
rauschma wrote: > > >> var c1 = Object.create(C); >> obj.one(); // 'A.foo' > > That would be c1.one(), right? > Yes, sorry edited post twice. rauschma wrote: > > > |here| === C and thus the search for super.one starts in B and finds > A.one. > >> B.two = function () { >> this.thre

Re: es-discuss Digest, Vol 52, Issue 117

2011-06-20 Thread Brendan Eich
On Jun 20, 2011, at 2:51 PM, Peter Michaux wrote: > By the way, I like this idea that "super" is available all the time > (not just in an initializer) like "this" is always available; however, > adding another implicit variable "here" which is dynamic like "this" > is disconcerting as "this" has b

Re: es-discuss Digest, Vol 52, Issue 117

2011-06-20 Thread Peter Michaux
On Mon, Jun 20, 2011 at 1:27 PM, Axel Rauschmayer wrote: > Terminology (created by me, but I think it explains well what is going on): > - |this| points to the object where property lookup starts. It always points > to the beginning of the prototype chain. > - |here| points to the object where a p

Re: es-discuss Digest, Vol 52, Issue 117

2011-06-20 Thread Axel Rauschmayer
Terminology (created by me, but I think it explains well what is going on): - |this| points to the object where property lookup starts. It always points to the beginning of the prototype chain. - |here| points to the object where a property was found. |here| can point to any object in the protot