<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments for Miško Hevery</title>
	<atom:link href="http://misko.hevery.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://misko.hevery.com</link>
	<description>Testability Explorer</description>
	<lastBuildDate>Thu, 19 Jan 2012 16:42:57 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>Comment on Dependency-Injection and JavaScript closures by Some useful readings &#124; Joshy&#039;s microblog</title>
		<link>http://misko.hevery.com/2010/05/29/dependency-injection-and-javascript-closures/comment-page-1/#comment-17513</link>
		<dc:creator>Some useful readings &#124; Joshy&#039;s microblog</dc:creator>
		<pubDate>Thu, 19 Jan 2012 16:42:57 +0000</pubDate>
		<guid isPermaLink="false">http://misko.hevery.com/?p=623#comment-17513</guid>
		<description>[...] http://misko.hevery.com/2010/05/29/dependency-injection-and-javascript-closures/ [...]</description>
		<content:encoded><![CDATA[<p>[...] <a href="http://misko.hevery.com/2010/05/29/dependency-injection-and-javascript-closures/" rel="nofollow">http://misko.hevery.com/2010/05/29/dependency-injection-and-javascript-closures/</a> [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Flaw: Constructor does Real Work by Dave Abrahams</title>
		<link>http://misko.hevery.com/code-reviewers-guide/flaw-constructor-does-real-work/comment-page-1/#comment-17387</link>
		<dc:creator>Dave Abrahams</dc:creator>
		<pubDate>Tue, 17 Jan 2012 16:24:56 +0000</pubDate>
		<guid isPermaLink="false">http://misko.hevery.com/?page_id=321#comment-17387</guid>
		<description>“It violates the Single Responsibility Principle,” while true, doesn&#039;t have any obvious connection to testability.  Could you explain that?

Thanks</description>
		<content:encoded><![CDATA[<p>“It violates the Single Responsibility Principle,” while true, doesn&#8217;t have any obvious connection to testability.  Could you explain that?</p>
<p>Thanks</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Flaw: Brittle Global State &amp; Singletons by Dave Abrahams</title>
		<link>http://misko.hevery.com/code-reviewers-guide/flaw-brittle-global-state-singletons/comment-page-1/#comment-17377</link>
		<dc:creator>Dave Abrahams</dc:creator>
		<pubDate>Tue, 17 Jan 2012 14:00:43 +0000</pubDate>
		<guid isPermaLink="false">http://misko.hevery.com/?page_id=328#comment-17377</guid>
		<description>On  &quot;JVM global state&quot; vs. &quot;Application shared state,&quot; I agree there is a distinction but AFAICT it is only a matter of degree.  The more sharing in an application, the more likely it is that you&#039;ll need to use one &quot;sharer&quot; to set up conditions for another &quot;sharer&quot; to be tested.  Or, you might easily fail to test the real conditions of your application because of an interaction that&#039;s hidden in that shared, mutable state.</description>
		<content:encoded><![CDATA[<p>On  &#8220;JVM global state&#8221; vs. &#8220;Application shared state,&#8221; I agree there is a distinction but AFAICT it is only a matter of degree.  The more sharing in an application, the more likely it is that you&#8217;ll need to use one &#8220;sharer&#8221; to set up conditions for another &#8220;sharer&#8221; to be tested.  Or, you might easily fail to test the real conditions of your application because of an interaction that&#8217;s hidden in that shared, mutable state.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Flaw: Class Does Too Much by Dave Abrahams</title>
		<link>http://misko.hevery.com/code-reviewers-guide/flaw-class-does-too-much/comment-page-1/#comment-17375</link>
		<dc:creator>Dave Abrahams</dc:creator>
		<pubDate>Tue, 17 Jan 2012 13:51:27 +0000</pubDate>
		<guid isPermaLink="false">http://misko.hevery.com/?page_id=332#comment-17375</guid>
		<description>This article fails to explain how, if I&#039;ve avoided the other three flaws, this particular flaw makes anything hard to test.  There are lots of good non-testing-related arguments for why classes shouldn&#039;t “do too much,” but how, specifically does it impact testability?</description>
		<content:encoded><![CDATA[<p>This article fails to explain how, if I&#8217;ve avoided the other three flaws, this particular flaw makes anything hard to test.  There are lots of good non-testing-related arguments for why classes shouldn&#8217;t “do too much,” but how, specifically does it impact testability?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Ask! by karolina</title>
		<link>http://misko.hevery.com/your-suggestions/comment-page-4/#comment-17357</link>
		<dc:creator>karolina</dc:creator>
		<pubDate>Tue, 17 Jan 2012 11:43:16 +0000</pubDate>
		<guid isPermaLink="false">http://misko.hevery.com/?page_id=122#comment-17357</guid>
		<description>Hi Misko,
two year ago we discussed your TTD-course at the Fac. of Math and Physics..during the time the situation changed and our vice-dean for informatics dept. is very interested in starting a new discussion about this matter..so, is your offer still valid?
regards, karolina</description>
		<content:encoded><![CDATA[<p>Hi Misko,<br />
two year ago we discussed your TTD-course at the Fac. of Math and Physics..during the time the situation changed and our vice-dean for informatics dept. is very interested in starting a new discussion about this matter..so, is your offer still valid?<br />
regards, karolina</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Move over Java, I have fallen in love with JavaScript by gmadar</title>
		<link>http://misko.hevery.com/2010/04/07/move-over-java-i-have-fallen-in-love-with-javascript/comment-page-1/#comment-17246</link>
		<dc:creator>gmadar</dc:creator>
		<pubDate>Mon, 16 Jan 2012 10:57:02 +0000</pubDate>
		<guid isPermaLink="false">http://misko.hevery.com/?p=616#comment-17246</guid>
		<description>like any other solution. it has it&#039;s good part and it&#039;s bad parts. But hey - I love JavaScript :)</description>
		<content:encoded><![CDATA[<p>like any other solution. it has it&#8217;s good part and it&#8217;s bad parts. But hey &#8211; I love JavaScript <img src='http://misko.hevery.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Static Methods are Death to Testability by David Zentgraf</title>
		<link>http://misko.hevery.com/2008/12/15/static-methods-are-death-to-testability/comment-page-1/#comment-16200</link>
		<dc:creator>David Zentgraf</dc:creator>
		<pubDate>Thu, 05 Jan 2012 04:28:58 +0000</pubDate>
		<guid isPermaLink="false">http://misko.hevery.com/?p=352#comment-16200</guid>
		<description>Static functions are only problematic if they have unseen dependencies (violate dependency injection principles) and are not idempotent (have state). It&#039;s not even about being leaf methods, that&#039;s just a recursive problem of my first sentence. Static methods are just functions. Functions are extremely easy to test if they&#039;re idempotent. That&#039;s the functional principle. Functions may call other functions as much as they like and it doesn&#039;t change anything about their being idempotent, as long as the functions they call are also idempotent. You can have a long chain of function calls hanging off of your static method, if none of them have any state there&#039;s no problem. That&#039;s why Math.abs() is easy to test, because it adheres to these principles. In the background it may make a thousand calls to hundreds of different functions, you don&#039;t need to care.

So your rant against static methods is really a straw man rant against non-idempotent global functions, hence global state. It has nothing to do with being static. Static functions are fine and useful in OOP.</description>
		<content:encoded><![CDATA[<p>Static functions are only problematic if they have unseen dependencies (violate dependency injection principles) and are not idempotent (have state). It&#8217;s not even about being leaf methods, that&#8217;s just a recursive problem of my first sentence. Static methods are just functions. Functions are extremely easy to test if they&#8217;re idempotent. That&#8217;s the functional principle. Functions may call other functions as much as they like and it doesn&#8217;t change anything about their being idempotent, as long as the functions they call are also idempotent. You can have a long chain of function calls hanging off of your static method, if none of them have any state there&#8217;s no problem. That&#8217;s why Math.abs() is easy to test, because it adheres to these principles. In the background it may make a thousand calls to hundreds of different functions, you don&#8217;t need to care.</p>
<p>So your rant against static methods is really a straw man rant against non-idempotent global functions, hence global state. It has nothing to do with being static. Static functions are fine and useful in OOP.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Ask! by Wouter de Kort</title>
		<link>http://misko.hevery.com/your-suggestions/comment-page-4/#comment-15984</link>
		<dc:creator>Wouter de Kort</dc:creator>
		<pubDate>Tue, 03 Jan 2012 10:26:17 +0000</pubDate>
		<guid isPermaLink="false">http://misko.hevery.com/?page_id=122#comment-15984</guid>
		<description>Hi Misko,

I would like to say that I&#039;m learning a lot by reading your blogs and looking at the presentations :)

I&#039;m only having a question about how to inject disposable items. 
I&#039;m a .NET developer and I use things like 
public class Presenter // Follows MVP pattern
{
....
public void DoStuff()
{
// Use a WCF service that should be closed properly (in test it&#039;s mocked so no WCF)
using(IMyService service = ServiceFactory.Instance.Create()) { } 
}
}
If I would pass service as a parameter, then the calling code would have to dispose of the service but the calling code is a codebehind file of my ASPX so that shouldn&#039;t know about services and things like that.

How would you handle this? Make the whole Presenter disposable and pass the service in the constructor (trough a factory) or... ?

Thanks!
Wouter</description>
		<content:encoded><![CDATA[<p>Hi Misko,</p>
<p>I would like to say that I&#8217;m learning a lot by reading your blogs and looking at the presentations <img src='http://misko.hevery.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>I&#8217;m only having a question about how to inject disposable items.<br />
I&#8217;m a .NET developer and I use things like<br />
public class Presenter // Follows MVP pattern<br />
{<br />
&#8230;.<br />
public void DoStuff()<br />
{<br />
// Use a WCF service that should be closed properly (in test it&#8217;s mocked so no WCF)<br />
using(IMyService service = ServiceFactory.Instance.Create()) { }<br />
}<br />
}<br />
If I would pass service as a parameter, then the calling code would have to dispose of the service but the calling code is a codebehind file of my ASPX so that shouldn&#8217;t know about services and things like that.</p>
<p>How would you handle this? Make the whole Presenter disposable and pass the service in the constructor (trough a factory) or&#8230; ?</p>
<p>Thanks!<br />
Wouter</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Dependency Injection Myth: Reference Passing by Are singletons pathalogical liars? &#124; Davelog</title>
		<link>http://misko.hevery.com/2008/10/21/dependency-injection-myth-reference-passing/comment-page-1/#comment-15750</link>
		<dc:creator>Are singletons pathalogical liars? &#124; Davelog</dc:creator>
		<pubDate>Sat, 31 Dec 2011 23:57:07 +0000</pubDate>
		<guid isPermaLink="false">http://misko.hevery.com/?p=252#comment-15750</guid>
		<description>[...] The response is apparently answered in the post Dependency Injection Myth: Reference Passing [...]</description>
		<content:encoded><![CDATA[<p>[...] The response is apparently answered in the post Dependency Injection Myth: Reference Passing [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Singletons are Pathological Liars by Are singletons pathalogical liars? &#124; Davelog</title>
		<link>http://misko.hevery.com/2008/08/17/singletons-are-pathological-liars/comment-page-2/#comment-15749</link>
		<dc:creator>Are singletons pathalogical liars? &#124; Davelog</dc:creator>
		<pubDate>Sat, 31 Dec 2011 23:48:33 +0000</pubDate>
		<guid isPermaLink="false">http://misko.hevery.com/?p=162#comment-15749</guid>
		<description>[...] Miško Hevery thinks so: Singletons are Pathological Liars. [...]</description>
		<content:encoded><![CDATA[<p>[...] Miško Hevery thinks so: Singletons are Pathological Liars. [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

