Created
July 26, 2011 15:09
-
-
Save jasonwyatt/1106973 to your computer and use it in GitHub Desktop.
Singleton Pattern with Require JS
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
define(function(){ | |
var instance = null; | |
function MySingleton(){ | |
if(instance !== null){ | |
throw new Error("Cannot instantiate more than one MySingleton, use MySingleton.getInstance()"); | |
} | |
this.initialize(); | |
} | |
MySingleton.prototype = { | |
initialize: function(){ | |
// summary: | |
// Initializes the singleton. | |
this.foo = 0; | |
this.bar = 1; | |
} | |
}; | |
MySingleton.getInstance = function(){ | |
// summary: | |
// Gets an instance of the singleton. It is better to use | |
if(instance === null){ | |
instance = new MySingleton(); | |
} | |
return instance; | |
}; | |
return MySingleton.getInstance(); | |
}); |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
@jasonwyatt Out of curiosity, is there a reason that getInstance is even necessary? Why can't we just have the constructor point to _instance and return that if it's not null? I.e., here is my revised version that seems to return the same object every time. Note that it makes use of the fact that you can use a constructor to return anything you want.
Seems to work for me... any reason you think this wouldn't be equivalent output-wise to yours? The upside to this is that it conforms more to the requirejs ecosystem and is easier to read.