views:

338

answers:

6

I run in to something that illustrates how I clearly don't get it yet.

Can anyone please explain why the value of "this" changes in the following?

var MyFunc = function(){
    alert(this);
    var innerFunc = function(){
        alert(this);
    }
    innerFunc();
};

new MyFunc();
A: 

At first glance I'd say it's because the outer 'this' is in reference to MyFunc and the inner 'this' is in reference to innerFunc.

However, Javascript isn't something I have any particular expertise in.

Carter
Carter, you must be new here... don't bother with the disclaimer! You don't need to have expertise in anything to answer it... look at me for example! ;-)
nickf
+16  A: 

In JavaScript, this represents the context object on which the function was called, not the scope in which it was defined (or the scope in which it was called). For MyFunc, this references the new object being created; but for innerFunc, it references the global object, since no context is specified when innerFunc is called.

This tends to trip up those used to Java or similar OO languages, where this almost always references an instance of the class on which the method being called is defined. Just remember: JavaScript doesn't have methods. Or classes. Just objects and functions.

See also: What is the rationale for the behavior of the ‘this’ keyword in JavaScript?

Shog9
Thanks Shog9. So, what's the relationship between "this" and scope/closure?
morgancodes
Little or none. `this` is scoped to a single function - it isn't inherited into the scope of other functions defined within that function. It's the context object a function is called on, nothing else.
Shog9
Ah, lovely javascript, continuing to reveal her mysteries to me. For years, I've been working on the assumption that "this" is searched for in the scope chain, just like any other variable. Those days are over!
morgancodes
+1  A: 

I believe you'll find the answer in this similar question I asked some time ago.

rmeador
+1  A: 

As a sidenote, "this" isn't necessarily referencing the actual function all the time, since you can invoke a function with a "forced" this-reference, think about an event-handler, in which this will refer to the actual element that fired the event.

using

yourFunction.apply(thisReference, arguments)

you can invoke it where "this" will point to whatever you pass on as first argument.

jishi
+1  A: 

For a detailed explanation of closures, visit:

http://www.brockman.se/writing/method-references.html.utf8

Mr. Brockman illustrates clearly the problem you are having. I read this article every now and again simply for the sheer pleasure of being able to say, "Aha! I get it!"

For even more interesting JavaScript lessons, visit Douglas Crockford's "Wrrrld Wide Web" at

http://www.crockford.com/

As the creator of JSON, Mr. Crockford is "The Man" when it comes to JavaScript. He does not know me, but he has mentored my understanding of the beauty of JavaScript, nay, of programming in general.

You are this close to becoming a much better programmer than you are now. I say thins not in a demeaning sense, but from knowing how these two authors challenged my own skills.

+2  A: 

Just do the following:

var MyFunc = function(){
    var self = this;
    alert(self);
    var innerFunc = function(){
        alert(self);
    }
    innerFunc();
};

new MyFunc();

This way self will always mean this, irrespective of where you're calling it from, which is usually what you want.

Rakesh Pai