<?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: Mock Objects for C++, Part 5</title>
	<atom:link href="http://blogs.ijw.co.nz/chris/index.php/2008/11/mock-objects-for-c-part-5/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.ijw.co.nz/chris/index.php/2008/11/mock-objects-for-c-part-5/</link>
	<description>Not quite a Yegge long.</description>
	<lastBuildDate>Wed, 16 Feb 2011 08:39:32 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.5</generator>
	<item>
		<title>By: Peter Bindels</title>
		<link>http://blogs.ijw.co.nz/chris/index.php/2008/11/mock-objects-for-c-part-5/comment-page-1/#comment-236</link>
		<dc:creator>Peter Bindels</dc:creator>
		<pubDate>Wed, 24 Dec 2008 11:10:31 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ijw.co.nz/chris/index.php/2008/11/mock-objects-for-c-part-5/#comment-236</guid>
		<description>As I&#039;ve just reacted to your previous comment, there&#039;s a much nicer way of doing this. Given a number of specializations of a template method, you can take the address of that method instantiated with the given argument types, let it put them in a tuple of sorts and send that along to your mocking base logic. If you also add a constant for each function (__LINE__ was my first guess - added a bug to MS Connect for it too as Microsoft considers it not constant) you can instantiate the template for each function separately and keep them separated (so your match matching will work properly too). That way it also works with stdcall functions, as well as thiscall and fastcall functions.</description>
		<content:encoded><![CDATA[<p>As I&#8217;ve just reacted to your previous comment, there&#8217;s a much nicer way of doing this. Given a number of specializations of a template method, you can take the address of that method instantiated with the given argument types, let it put them in a tuple of sorts and send that along to your mocking base logic. If you also add a constant for each function (__LINE__ was my first guess &#8211; added a bug to MS Connect for it too as Microsoft considers it not constant) you can instantiate the template for each function separately and keep them separated (so your match matching will work properly too). That way it also works with stdcall functions, as well as thiscall and fastcall functions.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Thiago</title>
		<link>http://blogs.ijw.co.nz/chris/index.php/2008/11/mock-objects-for-c-part-5/comment-page-1/#comment-234</link>
		<dc:creator>Thiago</dc:creator>
		<pubDate>Tue, 23 Dec 2008 22:10:12 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ijw.co.nz/chris/index.php/2008/11/mock-objects-for-c-part-5/#comment-234</guid>
		<description>There is another interesting framework, maybe useful in future parts:
MockItNow - http://www.rorydriscoll.com/mockitnow/

It has a different approach from AMOP and keep things simple.</description>
		<content:encoded><![CDATA[<p>There is another interesting framework, maybe useful in future parts:<br />
MockItNow &#8211; <a href="http://www.rorydriscoll.com/mockitnow/" rel="nofollow">http://www.rorydriscoll.com/mockitnow/</a></p>
<p>It has a different approach from AMOP and keep things simple.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

