Skip to main content

Does using method chaining in PHP cause any problems with resources or memory?



I'm talking about methods like this:







$object->method()->method1('param')->method2('param');







Those are created by returning the object in the function.







return $this;







I've seen third-party software use that method, but I'm wondering, wouldn't that cause a bit of a problem with the resources or memory because you're continuously returning the entire object?


Comments

  1. You are not returning the entire object, but rather a reference to the object -- that is, just the memory location where it resides. So objects aren't constantly being copied around in memory when methods are called along the chain.

    By default (mainly, but read the link for actual details), objects in PHP are passed, returned, and assigned by reference.

    See the PHP docs on references.

    ReplyDelete
  2. Chaining methods by returning the object is actually efficient.

    The stack does not grow bigger by adding new methods to the chain.

    PHP also does not return a copy of the object but a reference, it does not pass the object but a "pointer".

    ReplyDelete
  3. Those aren't "nested methods", but it's called method chaining and it shouldn't affect performance in anyway (your not going anyhow "deep in the stack").

    You can split the code into those pieces:

    $res = $object->method();
    $res = $res->method1('param')
    $res = $res->method2('param');
    // and res is still equivalent to $object if you return $this


    So no object copying, no nested calls, no many items in "call stack"... No performance overhead, you should be just fine.

    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