tags:

views:

107

answers:

4

Often I see a global object defined in javascript code to act as a namespace.

var MyNS = {a: function() {}, ... };

But sometimes, I see people leave off the "var" keyword like

MyNS = {a: function() {}, ...};

I believe in web browsers if you do not define a variable with var, it is put in the window object, which acts as a global namespace. Since it saves a few bytes of text by not using "var" is there a reason to use the keyword for this specific purpose ?

+2  A: 

The use of var defines a local variable in the current scope. If you're in the global scope, they are effectively equivalent. The use of var there is more for understandability and maintainability, as the intention is absolutely clear. It's less clear without initializing the var.

In any local scope, if MyNS is initialized somewhere up the scope chain, you'll be overwriting that local variable rather than defining a global variable.

eyelidlessness
A: 
Pointy
+5  A: 

Since it saves a few bytes of text by not using "var" is there a reason to use the keyword for this specific purpose ?

I wouldn't recommend you to avoid the var keyword, even if you are on Global Code.

The two ways seem similar but actually they are not the same, the first is a Variable Declaration, the Variable Object on global code, is the Global object itself, that's why global variables are accessible as properties of the global object (window.MyNS).

The second one is an undeclared assignment, it creates a property on the global object if the identifier is not found in the scope chain.

A real reason to avoid it is that in the new standard of the language, ECMAScript 5th Edition, under Strict Mode, an assignment to an undeclared identifier will throw a ReferenceError breaking your code.

There is also another subtle difference between your two examples, the Variable Instantiation creates the property on the global object that is non-deleteable:

var myVar = '';
delete window.myVar; // false
typeof window.myVar; // 'string'

While the undeclared assignment not:

myProp = '';
delete window.myProp; // true
typeof window.myProp; // 'undefined'

Recommended article:

CMS
+1 - Not only that, it is just plain sloppy. If you want to save a few bytes just minify the code.
ChaosPandion
So can we also declare the global variable by `window.MyNS={};` and have the exactly same implication as `var MyNS={};` ?
c411
@Piccolo, well, not exactly *the same*, `window.MyNS = {};` will create a *property* on the global object, while `var MyNS = {};` will declare a variable, and as the global object, is the Variable Object of the Global Execution Context, a global property will be also created as consequence, I would recommend you give a look to the article I link in the answer.
CMS
A: 

Douglas Crockford on this exact question: http://www.yuiblog.com/blog/2008/04/16/global-domination-part-two/

He settles on using a comment with the initialization, but without var. His analysis of the trade-offs is worth reading even if you disagree.

Gabe Moothart
I'm a fan of Mr. Crockford but IHMO this is one of his **worst** articles. The three ways he describes are *not completely equivalent*, and there are *possible hazards* of using an *undeclared* assignment (the third way) under ES5 strict mode, moreover, his JSLint tool encourages the `"use strict"` directive without checking almost none of the rules of strict more :(
CMS