Comments on: Real programming with PHP 5.3 (part 4): A more realistic example http://blog.agilephp.com/2009/06/02/real-programming-with-php-53-part-4-a-more-realistic-example/ Dagfinn Reiersøl on PHP, agile development, Ruby and other addictive substances Fri, 23 Jul 2010 20:17:39 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: Ionut G. Stan http://blog.agilephp.com/2009/06/02/real-programming-with-php-53-part-4-a-more-realistic-example/comment-page-1/#comment-619 Ionut G. Stan Tue, 09 Jun 2009 11:00:14 +0000 http://blog.agilephp.com/?p=1580#comment-619 I'm wondering if this approach doesn't have the same problem as in JavaScript, i.e. it is better to associate functions with an instance through the prototype (in PHP that would be the "old" way) than to create a function object for each instance of the class. I mainly see functions bound to classes for monkey-patching than for use cases like yours when there is basically no benefit. I’m wondering if this approach doesn’t have the same problem as in JavaScript, i.e. it is better to associate functions with an instance through the prototype (in PHP that would be the “old” way) than to create a function object for each instance of the class.

I mainly see functions bound to classes for monkey-patching than for use cases like yours when there is basically no benefit.

]]>