The problem here is not the Module Pattern, but rather that whenever you use setTimeout to call a function after a certain period of time has elapsed, this function gets executed in the ‘window’ context. In other words, inside that function, the keyword ‘this’ will always reference the global window object.

If you would, instead, call pubFun2 directly, ‘this’ would point to NS1, like:

NS1.pubFun2(); // will execute pubFun1 from within pubFun2

If you have or absolutely want to use setTimeout, you can use ‘call’:

setTimeout(function() { NS1.pubFun2.call(NS1); } , 1000);

The ‘call’ function lets you call any function in a predefined scope, so the statement above essentially means:

“Execute the function pubFun2 after a delay of 1000 milliseconds and make the ‘this’ keyword inside that function reference NS1″.

MDC provides some further explanation about call.

I hope that makes sense.

Klaus

var NS1 = function() {
var privFun = function() {…};
return {
pubFun1 : function() {…},
pubFun2 : function() {
this.pubFun1();
…
}
};
}();

setTimeout(NS1.pubFun2, 1000); //ERROR: this.pubFun1 not a function.

So I tend to do it like this…

var NS1 = function() {
var privFun = function() {…};
var me = {
pubFun1 : function() {…},
pubFun2 : function() {
me.pubFun1();
…
}
};
return me;
}();
setTimeout(NS1.pubFun2, 1000); //OK

What are your thoughts on this (advantages/disadvantages) and is there another way of doing the same thing?

clone: function (arr)
{
if(typeof(arr)==’null’ || typeof(arr)==’undefined’)
return new Object();

var i, _i, temp;
if(typeof arr !== ‘object’)
return arr;

else
{
if(arr.concat)
{
temp = [];
for(i = 0, _i = arr.length; i < _i; i++)
temp[i] = arguments.callee(arr[i]);
}
else
{
temp = {};
for(i in arr)
temp[i] = arguments.callee(arr[i]);

}
return temp;
}
}