<?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 on: Custom Matchers in NMock 2.0</title>
	<atom:link href="http://vaderpi.com/blog/?feed=rss2&#038;p=307" rel="self" type="application/rss+xml" />
	<link>http://vaderpi.com/blog/?p=307</link>
	<description>babblings!</description>
	<lastBuildDate>Mon, 24 May 2010 18:07:59 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: vaderpi</title>
		<link>http://vaderpi.com/blog/?p=307&#038;cpage=1#comment-2924</link>
		<dc:creator>vaderpi</dc:creator>
		<pubDate>Mon, 27 Feb 2006 20:40:44 +0000</pubDate>
		<guid isPermaLink="false">http://vaderpi.scottandlaurie.com/blog/?p=307#comment-2924</guid>
		<description>Thanks for the input, Nat. I will update this tutorial to reflect your comments. And I will include your guidelines in the tutorial as well.</description>
		<content:encoded><![CDATA[<p>Thanks for the input, Nat. I will update this tutorial to reflect your comments. And I will include your guidelines in the tutorial as well.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nat</title>
		<link>http://vaderpi.com/blog/?p=307&#038;cpage=1#comment-2923</link>
		<dc:creator>Nat</dc:creator>
		<pubDate>Mon, 27 Feb 2006 17:18:10 +0000</pubDate>
		<guid isPermaLink="false">http://vaderpi.scottandlaurie.com/blog/?p=307#comment-2923</guid>
		<description>One more thing... when writing a custom matcher, it&#039;s considered good style to create a factory method (or at least use a variable) that has a name that reveals what the matcher does.  See the jMock tutorial on writing Custom Constraints for more information (http://www.jmock.org/custom-constraints.html).</description>
		<content:encoded><![CDATA[<p>One more thing&#8230; when writing a custom matcher, it&#8217;s considered good style to create a factory method (or at least use a variable) that has a name that reveals what the matcher does.  See the jMock tutorial on writing Custom Constraints for more information (<a href="http://www.jmock.org/custom-constraints.html" rel="nofollow">http://www.jmock.org/custom-constraints.html</a>).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nat</title>
		<link>http://vaderpi.com/blog/?p=307&#038;cpage=1#comment-2922</link>
		<dc:creator>Nat</dc:creator>
		<pubDate>Mon, 27 Feb 2006 17:16:53 +0000</pubDate>
		<guid isPermaLink="false">http://vaderpi.scottandlaurie.com/blog/?p=307#comment-2922</guid>
		<description>It&#039;s not a good idea to use Matchers to capture parameters.  NMock-2 expects that matchers are stateless.  It calls them during the dispatch of every invocation and so you don&#039;t have a guarantee what exactly will be captured.  If you want to capture a parameter value, write an *Action* instead.</description>
		<content:encoded><![CDATA[<p>It&#8217;s not a good idea to use Matchers to capture parameters.  NMock-2 expects that matchers are stateless.  It calls them during the dispatch of every invocation and so you don&#8217;t have a guarantee what exactly will be captured.  If you want to capture a parameter value, write an *Action* instead.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
