Comments on: Enforcing `new` in constructors http://www.jspatterns.com/enforcing-new-in-constructors/ Exploring common JavaScript patterns and anti-patterns Fri, 03 Feb 2012 21:54:54 +0000 hourly 1 http://wordpress.org/?v=3.0.3 By: Dre Beats Headphones http://www.jspatterns.com/enforcing-new-in-constructors/#comment-41813 Dre Beats Headphones Fri, 16 Dec 2011 04:33:50 +0000 http://www.jspatterns.com/?p=53#comment-41813 Just added this blog to my favorites. I enjoy reading your blogs and hope you maintain them coming! Just added this blog to my favorites. I enjoy reading your blogs and hope you maintain them coming!

]]> By: Mira http://www.jspatterns.com/enforcing-new-in-constructors/#comment-6720 Mira Mon, 08 Nov 2010 17:02:58 +0000 http://www.jspatterns.com/?p=53#comment-6720 function MyClass(name) { if (!(this instanceof MyClass)) return new MyClass(); this.name = name; // more initialisation return this; } function MyClass(name) {
if (!(this instanceof MyClass)) return new MyClass();

this.name = name;
// more initialisation

return this;
}

]]> By: Phoscur http://www.jspatterns.com/enforcing-new-in-constructors/#comment-2181 Phoscur Mon, 22 Feb 2010 00:38:21 +0000 http://www.jspatterns.com/?p=53#comment-2181 function Constructor() { var that = (this === window) ? {} : this; ... return that; } I hope you aren't serious with this. It just doesn't make sense, as JavaScript always invokes the function as a non-constructor (if you put a new before just doesn't matter) because it returns something. The condition is always true and thereby unneeded. function Constructor() {
var that = (this === window) ? {} : this;
…
return that;
}
I hope you aren’t serious with this. It just doesn’t make sense, as JavaScript always invokes the function as a non-constructor (if you put a new before just doesn’t matter) because it returns something. The condition is always true and thereby unneeded.

]]>