Skip to main content

Using "return" when creating objects with "new"


I found something very odd today: If you create objects with a constructor function and the new keyword, but return a function from the constructor, it behaves like so:



  1. The newly-created "object" is instead a function.

  2. That new function can be invoked like normal, however...

  3. If you maintain a reference to this in the constructor function, this references an object that was correctly created from the constructor. It's what you expected to be returned from new .



Here's an example:




function Constructor() {
var self = this;

this.name = 'instance';
return function() {
return self;
}
}



So if you instantiated it like this: var instance = new Constructor() The following would result:




typeof instance //returns "function"
typeof instance() //returns "object"
instance() //returns { name: 'instance' }



So I guess I have three questions:



  1. Is this legal and does it work cross-browser? It's really awesome and I think it can be used in a lot of ways, but is this behavior dependable?

  2. What happens in the background that causes this behavior?

  3. (maybe answered by 2, but...) Is the new object (the one referenced with 'this') inside the new instance, so that it's all self-contained and is cleaned up properly by the garbage collector?


Source: Tips4allCCNA FINAL EXAM

Comments

  1. Well, that is a really good question and, as you may have guessed, not easily answered.

    To put it very simply:
    1) Yes and Yes; this is one of the amazing features you don't find in "traditional" programming languages.
    2) please read about closures (links below)
    3) Yes (please read more)

    You should read more about Javascript Closures:
    http://jibbering.com/faq/notes/closures/
    http://www.javascriptkit.com/javatutors/closures.shtml (here you got some good working examples)

    and, more particularly, the Parasitic Inheritance model:
    http://blog.higher-order.net/2008/02/21/javascript-parasitic-inheritance-power-constructors-and-instanceof/

    I hope this helps

    ReplyDelete
  2. this is what you call a closure

    what it does is create a self-contained code environment (commonly known as an object)

    typeof instance //returns "function" - since it's not "fired" or called. just returns the function declaration (correct me if i'm wrong)
    typeof instance() //returns "object" - it returns an object since you called it
    instance() //returns an object also - you called it, but you didn't store it


    an example of an object built using a closure:

    function Constructor() {
    var privateProperty = 'private';
    var privateMethod = function(){
    alert('called from public method');
    };

    //return only what's to be seen in public
    return {
    publicProperty: 'im public',
    publicMethod: function(){
    alert('called from public method');
    }
    getter: privateMethod //assign to call the private method
    }
    }

    var myObj = Constructor();
    var pubProp = myObj.publicProperty; // pubProp = 'im public'
    myObj.publicMethod() //alert: 'called from public method';
    myObj.getter() //alert: 'called from public method';

    //cannot access since "private":
    myObj.privateProperty
    myObj.privateMethod

    ReplyDelete

Post a Comment

Popular posts from this blog

[韓日関係] 首相含む大幅な内閣改造の可能性…早ければ来月10日ごろ=韓国

div not scrolling properly with slimScroll plugin

I am using the slimScroll plugin for jQuery by Piotr Rochala Which is a great plugin for nice scrollbars on most browsers but I am stuck because I am using it for a chat box and whenever the user appends new text to the boxit does scroll using the .scrollTop() method however the plugin's scrollbar doesnt scroll with it and when the user wants to look though the chat history it will start scrolling from near the top. I have made a quick demo of my situation http://jsfiddle.net/DY9CT/2/ Does anyone know how to solve this problem?

Why does this javascript based printing cause Safari to refresh the page?

The page I am working on has a javascript function executed to print parts of the page. For some reason, printing in Safari, causes the window to somehow update. I say somehow, because it does not really refresh as in reload the page, but rather it starts the "rendering" of the page from start, i.e. scroll to top, flash animations start from 0, and so forth. The effect is reproduced by this fiddle: http://jsfiddle.net/fYmnB/ Clicking the print button and finishing or cancelling a print in Safari causes the screen to "go white" for a sec, which in my real website manifests itself as something "like" a reload. While running print button with, let's say, Firefox, just opens and closes the print dialogue without affecting the fiddle page in any way. Is there something with my way of calling the browsers print method that causes this, or how can it be explained - and preferably, avoided? P.S.: On my real site the same occurs with Chrome. In the ex