<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Software Integrity Ltd</title>
	<atom:link href="http://software-integrity.com/blog/feed/" rel="self" type="application/rss+xml" />
	<link>http://software-integrity.com/blog</link>
	<description>Realtime and Embedded Software</description>
	<lastBuildDate>Fri, 21 Oct 2011 17:32:38 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>WCP: How does your software stack up?</title>
		<link>http://software-integrity.com/blog/2011/10/18/wcp-how-does-your-software-stack-up/</link>
		<comments>http://software-integrity.com/blog/2011/10/18/wcp-how-does-your-software-stack-up/#comments</comments>
		<pubDate>Tue, 18 Oct 2011 10:07:21 +0000</pubDate>
		<dc:creator>Peter Bushell</dc:creator>
				<category><![CDATA[Software Design]]></category>
		<category><![CDATA[WCP]]></category>

		<guid isPermaLink="false">http://software-integrity.com/blog/?p=774</guid>
		<description><![CDATA[When we link our programs together, the success of the operation reassures us that all our code and our static and global(?!) variables fit into the available memory. But what about the function parameters, the local variables and various other unknowns which go on the stack? When someone mentions dynamic memory allocation, the worst-casers amongst [...]
Related posts:<ol>
<li><a href='http://software-integrity.com/blog/2011/09/08/wcp-the-worst-case-principle/' rel='bookmark' title='WCP: The Worst Case Principle'>WCP: The Worst Case Principle</a></li>
</ol>]]></description>
		<wfw:commentRss>http://software-integrity.com/blog/2011/10/18/wcp-how-does-your-software-stack-up/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>ARM Cortex PendSV problem &amp; solution(?)</title>
		<link>http://software-integrity.com/blog/2011/09/27/arm-cortex-pendsv-problem-solution/</link>
		<comments>http://software-integrity.com/blog/2011/09/27/arm-cortex-pendsv-problem-solution/#comments</comments>
		<pubDate>Tue, 27 Sep 2011 10:00:50 +0000</pubDate>
		<dc:creator>Peter Bushell</dc:creator>
				<category><![CDATA[No Category]]></category>

		<guid isPermaLink="false">http://software-integrity.com/blog/?p=765</guid>
		<description><![CDATA[Anyone using PendSV on Cortex (e.g. to implement an RTOS scheduler) should read this! [Edited 29/09/11] It appears that there may or may not be a problem; the argument continues on the Embedded Gurus blog. If you&#8217;re tinkering with PendSV, it would be good to read the article (and the comments to it) anyway. &#160; [...]
No related posts.]]></description>
		<wfw:commentRss>http://software-integrity.com/blog/2011/09/27/arm-cortex-pendsv-problem-solution/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>WCP: Uncertain Times&#8230;</title>
		<link>http://software-integrity.com/blog/2011/09/20/wcp-uncertain-times/</link>
		<comments>http://software-integrity.com/blog/2011/09/20/wcp-uncertain-times/#comments</comments>
		<pubDate>Tue, 20 Sep 2011 17:00:08 +0000</pubDate>
		<dc:creator>Peter Bushell</dc:creator>
				<category><![CDATA[Software Design]]></category>
		<category><![CDATA[WCP]]></category>

		<guid isPermaLink="false">http://software-integrity.com/blog/?p=738</guid>
		<description><![CDATA[Timing issues are often important in systems containing software but, ultimately, all timing is determined by hardware. Let&#8217;s pursue this by splitting a hypothetical system into (1) the software we&#8217;re designing and (2) the platform it&#8217;s intended to run on. We also need to consider (3) the toolchain. To be a little more precise: The [...]
No related posts.]]></description>
		<wfw:commentRss>http://software-integrity.com/blog/2011/09/20/wcp-uncertain-times/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>WCP: The Worst Case Principle</title>
		<link>http://software-integrity.com/blog/2011/09/08/wcp-the-worst-case-principle/</link>
		<comments>http://software-integrity.com/blog/2011/09/08/wcp-the-worst-case-principle/#comments</comments>
		<pubDate>Thu, 08 Sep 2011 17:26:11 +0000</pubDate>
		<dc:creator>Peter Bushell</dc:creator>
				<category><![CDATA[Software Design]]></category>
		<category><![CDATA[WCP]]></category>

		<guid isPermaLink="false">http://software-integrity.com/blog/?p=730</guid>
		<description><![CDATA[My last article, Whatever Happened to the Worst Case?, was a bit of a rant but it promised further articles on the subject. This is the first of these, which does no more than describe what I mean by the &#8220;Worst Case Principle&#8221;, or WCP. I am using WCP as both a label in the [...]
Related posts:<ol>
<li><a href='http://software-integrity.com/blog/2011/08/25/whatever-happened-to-the-worst-case/' rel='bookmark' title='Whatever Happened to the Worst Case?'>Whatever Happened to the Worst Case?</a></li>
<li><a href='http://software-integrity.com/blog/2011/10/18/wcp-how-does-your-software-stack-up/' rel='bookmark' title='WCP: How does your software stack up?'>WCP: How does your software stack up?</a></li>
</ol>]]></description>
		<wfw:commentRss>http://software-integrity.com/blog/2011/09/08/wcp-the-worst-case-principle/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Whatever Happened to the Worst Case?</title>
		<link>http://software-integrity.com/blog/2011/08/25/whatever-happened-to-the-worst-case/</link>
		<comments>http://software-integrity.com/blog/2011/08/25/whatever-happened-to-the-worst-case/#comments</comments>
		<pubDate>Thu, 25 Aug 2011 15:37:44 +0000</pubDate>
		<dc:creator>Peter Bushell</dc:creator>
				<category><![CDATA[Software Design]]></category>
		<category><![CDATA[WCP]]></category>

		<guid isPermaLink="false">http://software-integrity.com/blog/?p=719</guid>
		<description><![CDATA[I&#8217;m dismayed about sloppy attitudes to design. I suspect they&#8217;re creeping across from consumer-focused software, where raw average speed is everything and an occasional glitch doesn&#8217;t matter. Well, I&#8217;m sorry, but as that kind of thinking creeps towards the vehicles I may travel in, or possibly the new nuclear power plant to be commissioned up [...]
Related posts:<ol>
<li><a href='http://software-integrity.com/blog/2011/09/08/wcp-the-worst-case-principle/' rel='bookmark' title='WCP: The Worst Case Principle'>WCP: The Worst Case Principle</a></li>
<li><a href='http://software-integrity.com/blog/2011/10/18/wcp-how-does-your-software-stack-up/' rel='bookmark' title='WCP: How does your software stack up?'>WCP: How does your software stack up?</a></li>
</ol>]]></description>
		<wfw:commentRss>http://software-integrity.com/blog/2011/08/25/whatever-happened-to-the-worst-case/feed/</wfw:commentRss>
		<slash:comments>7</slash:comments>
		</item>
		<item>
		<title>Documenting Code with Doxygen</title>
		<link>http://software-integrity.com/blog/2011/06/17/documenting-code-with-doxygen/</link>
		<comments>http://software-integrity.com/blog/2011/06/17/documenting-code-with-doxygen/#comments</comments>
		<pubDate>Fri, 17 Jun 2011 11:33:31 +0000</pubDate>
		<dc:creator>Peter Bushell</dc:creator>
				<category><![CDATA[C/C++]]></category>
		<category><![CDATA[Code documentation]]></category>

		<guid isPermaLink="false">http://software-integrity.com/blog/?p=703</guid>
		<description><![CDATA[My last post, quite a while ago, expressed my preference for putting usage comments (as opposed to implementation comments), as far as possible, in header files on the grounds that the header file is the primary interface which the user has with the code. The code file (.c or .cpp), from a user&#8217;s perspective, contains [...]
Related posts:<ol>
<li><a href='http://software-integrity.com/blog/2010/11/12/documenting-code/' rel='bookmark' title='Documenting Code'>Documenting Code</a></li>
</ol>]]></description>
		<wfw:commentRss>http://software-integrity.com/blog/2011/06/17/documenting-code-with-doxygen/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Documenting Code</title>
		<link>http://software-integrity.com/blog/2010/11/12/documenting-code/</link>
		<comments>http://software-integrity.com/blog/2010/11/12/documenting-code/#comments</comments>
		<pubDate>Fri, 12 Nov 2010 10:43:49 +0000</pubDate>
		<dc:creator>Peter Bushell</dc:creator>
				<category><![CDATA[C/C++]]></category>
		<category><![CDATA[Code documentation]]></category>

		<guid isPermaLink="false">http://software-integrity.com/blog/?p=670</guid>
		<description><![CDATA[An excellent and succinct article by Michael Barr entitled &#8220;What Belongs in a C .h Header File?&#8221; triggered the thoughts I am about to write down, for he forgot to mention comments as worthy items to be included. When conducting Advanced C courses, as I sometimes do, I have always emphasised the need for usage [...]
Related posts:<ol>
<li><a href='http://software-integrity.com/blog/2011/06/17/documenting-code-with-doxygen/' rel='bookmark' title='Documenting Code with Doxygen'>Documenting Code with Doxygen</a></li>
</ol>]]></description>
		<wfw:commentRss>http://software-integrity.com/blog/2010/11/12/documenting-code/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Exclusion Is Not Always Mutual</title>
		<link>http://software-integrity.com/blog/2010/06/26/exclusion-is-not-always-mutual/</link>
		<comments>http://software-integrity.com/blog/2010/06/26/exclusion-is-not-always-mutual/#comments</comments>
		<pubDate>Sat, 26 Jun 2010 13:58:43 +0000</pubDate>
		<dc:creator>Peter Bushell</dc:creator>
				<category><![CDATA[Mutual Exclusion]]></category>

		<guid isPermaLink="false">http://software-integrity.com/blog/?p=649</guid>
		<description><![CDATA[Most embedded software practitioners &#8211; sadly, not all &#8211; know that some form of what is normally called &#8220;Mutual Exclusion&#8221; is necessary when a read-write resource is shared among two or more concurrent activities, particularly (but not necessarily only) when test-and-set operations are involved. The expression &#8220;Mutual Exclusion&#8221; is so entrenched as a generic concept [...]
No related posts.]]></description>
		<wfw:commentRss>http://software-integrity.com/blog/2010/06/26/exclusion-is-not-always-mutual/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>New version of dynamic memory software for C++</title>
		<link>http://software-integrity.com/blog/2010/05/09/new-version-of-dynamic-memory-software-for-c/</link>
		<comments>http://software-integrity.com/blog/2010/05/09/new-version-of-dynamic-memory-software-for-c/#comments</comments>
		<pubDate>Sun, 09 May 2010 20:07:31 +0000</pubDate>
		<dc:creator>Peter Bushell</dc:creator>
				<category><![CDATA[Dynamic memory allocation]]></category>
		<category><![CDATA[C/C++]]></category>
		<category><![CDATA[Free software]]></category>

		<guid isPermaLink="false">http://software-integrity.com/blog/?p=633</guid>
		<description><![CDATA[Since Easter, when I promised a new release of this software, I&#8217;ve been exceptionally busy in a money-earning sort of way. I&#8217;ve noticed that others are blogging less now that their business has (presumably) picked up, so I&#8217;m not alone in disappointing my readers, but that is no excuse and so I have just uploaded [...]
Related posts:<ol>
<li><a href='http://software-integrity.com/blog/2010/03/08/free-software-thwarted-by-g/' rel='bookmark' title='Free software: thwarted by g++'>Free software: thwarted by g++</a></li>
<li><a href='http://software-integrity.com/blog/2010/01/28/free-software/' rel='bookmark' title='Free software!'>Free software!</a></li>
<li><a href='http://software-integrity.com/blog/2010/02/04/free-software-updated/' rel='bookmark' title='Free software updated'>Free software updated</a></li>
</ol>]]></description>
		<wfw:commentRss>http://software-integrity.com/blog/2010/05/09/new-version-of-dynamic-memory-software-for-c/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>The Mysteries of C++</title>
		<link>http://software-integrity.com/blog/2010/03/28/the-mysteries-of-c/</link>
		<comments>http://software-integrity.com/blog/2010/03/28/the-mysteries-of-c/#comments</comments>
		<pubDate>Sun, 28 Mar 2010 18:34:46 +0000</pubDate>
		<dc:creator>Peter Bushell</dc:creator>
				<category><![CDATA[C/C++]]></category>

		<guid isPermaLink="false">http://software-integrity.com/blog/?p=607</guid>
		<description><![CDATA[I like C++, but sometimes it appears to work with the aid of magic which I don&#8217;t fully understand. Last time (was it really 3 weeks ago?) I mentioned a problem I had with compiling the software I have been offering to subscribers to this blog with the GNU compiler. Or, to put it more [...]
No related posts.]]></description>
		<wfw:commentRss>http://software-integrity.com/blog/2010/03/28/the-mysteries-of-c/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Free software: thwarted by g++</title>
		<link>http://software-integrity.com/blog/2010/03/08/free-software-thwarted-by-g/</link>
		<comments>http://software-integrity.com/blog/2010/03/08/free-software-thwarted-by-g/#comments</comments>
		<pubDate>Mon, 08 Mar 2010 17:54:04 +0000</pubDate>
		<dc:creator>Peter Bushell</dc:creator>
				<category><![CDATA[Dynamic memory allocation]]></category>
		<category><![CDATA[C/C++]]></category>
		<category><![CDATA[Free software]]></category>

		<guid isPermaLink="false">http://software-integrity.com/blog/?p=603</guid>
		<description><![CDATA[The free software you may have downloaded from this site embodies an error of principle (details another time). It compiles with VC++ and IAR (ARM), and the code is correct and runs properly. However, I tried g++ today and it was less forgiving. Unfortunately, it&#8217;s right and I&#8217;m wrong, even though I got away with [...]
Related posts:<ol>
<li><a href='http://software-integrity.com/blog/2010/01/28/free-software/' rel='bookmark' title='Free software!'>Free software!</a></li>
<li><a href='http://software-integrity.com/blog/2010/02/04/free-software-updated/' rel='bookmark' title='Free software updated'>Free software updated</a></li>
<li><a href='http://software-integrity.com/blog/2010/05/09/new-version-of-dynamic-memory-software-for-c/' rel='bookmark' title='New version of dynamic memory software for C++'>New version of dynamic memory software for C++</a></li>
</ol>]]></description>
		<wfw:commentRss>http://software-integrity.com/blog/2010/03/08/free-software-thwarted-by-g/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Free software updated</title>
		<link>http://software-integrity.com/blog/2010/02/04/free-software-updated/</link>
		<comments>http://software-integrity.com/blog/2010/02/04/free-software-updated/#comments</comments>
		<pubDate>Thu, 04 Feb 2010 13:21:02 +0000</pubDate>
		<dc:creator>Peter Bushell</dc:creator>
				<category><![CDATA[Dynamic memory allocation]]></category>
		<category><![CDATA[Free software]]></category>

		<guid isPermaLink="false">http://software-integrity.com/blog/?p=551</guid>
		<description><![CDATA[The C++ dynamic memory software I published last week has been updated with a small but useful enhancement. Find out more by downloading it: start by going to the Subscribers&#8217; page. Related posts: Free software! Free software: thwarted by g++ New version of dynamic memory software for C++
Related posts:<ol>
<li><a href='http://software-integrity.com/blog/2010/01/28/free-software/' rel='bookmark' title='Free software!'>Free software!</a></li>
<li><a href='http://software-integrity.com/blog/2010/03/08/free-software-thwarted-by-g/' rel='bookmark' title='Free software: thwarted by g++'>Free software: thwarted by g++</a></li>
<li><a href='http://software-integrity.com/blog/2010/05/09/new-version-of-dynamic-memory-software-for-c/' rel='bookmark' title='New version of dynamic memory software for C++'>New version of dynamic memory software for C++</a></li>
</ol>]]></description>
		<wfw:commentRss>http://software-integrity.com/blog/2010/02/04/free-software-updated/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Free software!</title>
		<link>http://software-integrity.com/blog/2010/01/28/free-software/</link>
		<comments>http://software-integrity.com/blog/2010/01/28/free-software/#comments</comments>
		<pubDate>Thu, 28 Jan 2010 16:56:20 +0000</pubDate>
		<dc:creator>Peter Bushell</dc:creator>
				<category><![CDATA[Dynamic memory allocation]]></category>
		<category><![CDATA[News]]></category>
		<category><![CDATA[Free software]]></category>

		<guid isPermaLink="false">http://software-integrity.com/blog/?p=527</guid>
		<description><![CDATA[For the last couple of months, my software efforts have been diluted by the need to attend to other matters no less important but somewhat distracting. Now I have finally released some software. It is not the whole of SKC++, though. I learned so many things, at a detailed level (mainly about C++), in developing [...]
Related posts:<ol>
<li><a href='http://software-integrity.com/blog/2010/02/04/free-software-updated/' rel='bookmark' title='Free software updated'>Free software updated</a></li>
<li><a href='http://software-integrity.com/blog/2010/03/08/free-software-thwarted-by-g/' rel='bookmark' title='Free software: thwarted by g++'>Free software: thwarted by g++</a></li>
<li><a href='http://software-integrity.com/blog/2010/05/09/new-version-of-dynamic-memory-software-for-c/' rel='bookmark' title='New version of dynamic memory software for C++'>New version of dynamic memory software for C++</a></li>
</ol>]]></description>
		<wfw:commentRss>http://software-integrity.com/blog/2010/01/28/free-software/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Automatic registration now open</title>
		<link>http://software-integrity.com/blog/2010/01/20/automatic-registration-now-open/</link>
		<comments>http://software-integrity.com/blog/2010/01/20/automatic-registration-now-open/#comments</comments>
		<pubDate>Wed, 20 Jan 2010 10:43:27 +0000</pubDate>
		<dc:creator>Peter Bushell</dc:creator>
				<category><![CDATA[News]]></category>

		<guid isPermaLink="false">http://software-integrity.com/blog/?p=499</guid>
		<description><![CDATA[You can now register automatically as a Subscriber to this blog. Just go to the &#8220;Subscribers&#8221; page and follow the instructions there. The previous posting tells you why you might want to subscribe. Related posts: This blog is now open to subscription Free software!
Related posts:<ol>
<li><a href='http://software-integrity.com/blog/2010/01/16/this-blog-is-now-open-to-subscription/' rel='bookmark' title='This blog is now open to subscription'>This blog is now open to subscription</a></li>
<li><a href='http://software-integrity.com/blog/2010/01/28/free-software/' rel='bookmark' title='Free software!'>Free software!</a></li>
</ol>]]></description>
		<wfw:commentRss>http://software-integrity.com/blog/2010/01/20/automatic-registration-now-open/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>This blog is now open to subscription</title>
		<link>http://software-integrity.com/blog/2010/01/16/this-blog-is-now-open-to-subscription/</link>
		<comments>http://software-integrity.com/blog/2010/01/16/this-blog-is-now-open-to-subscription/#comments</comments>
		<pubDate>Sat, 16 Jan 2010 14:22:09 +0000</pubDate>
		<dc:creator>Peter Bushell</dc:creator>
				<category><![CDATA[News]]></category>

		<guid isPermaLink="false">http://software-integrity.com/blog/?p=496</guid>
		<description><![CDATA[It is now possible to subscribe to this blog. Subscribers (only) will be able to download various pieces of software which I will begin soon to make available. Subscribers will also be able to see any private blog entries I might make, which will be invisible to casual visitors. I experimented, yesterday, with automatic registration [...]
Related posts:<ol>
<li><a href='http://software-integrity.com/blog/2010/01/20/automatic-registration-now-open/' rel='bookmark' title='Automatic registration now open'>Automatic registration now open</a></li>
<li><a href='http://software-integrity.com/blog/2010/01/28/free-software/' rel='bookmark' title='Free software!'>Free software!</a></li>
</ol>]]></description>
		<wfw:commentRss>http://software-integrity.com/blog/2010/01/16/this-blog-is-now-open-to-subscription/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>SKC++: No semaphores!</title>
		<link>http://software-integrity.com/blog/2010/01/07/skc-no-semaphores/</link>
		<comments>http://software-integrity.com/blog/2010/01/07/skc-no-semaphores/#comments</comments>
		<pubDate>Thu, 07 Jan 2010 15:17:46 +0000</pubDate>
		<dc:creator>Peter Bushell</dc:creator>
				<category><![CDATA[Projects]]></category>
		<category><![CDATA[RTOS]]></category>
		<category><![CDATA[SKC++]]></category>
		<category><![CDATA[Synchronisation]]></category>

		<guid isPermaLink="false">http://software-integrity.com/blog/?p=464</guid>
		<description><![CDATA[Hypothesis: SKC++ doesn&#8217;t need semaphores. If you disagree with this, please comment, with supporting arguments. In the meantime, I&#8217;ll present a few arguments of my own, supporting this hypothesis, though I&#8217;m not enough of a mathematician to establish it as a law &#8211; or even as a theory. I emphasise that I&#8217;m talking here about [...]
Related posts:<ol>
<li><a href='http://software-integrity.com/blog/2009/10/19/skc-tasks-and-timers/' rel='bookmark' title='SKC++: Tasks and Timers'>SKC++: Tasks and Timers</a></li>
<li><a href='http://software-integrity.com/blog/2009/10/14/skc-event-handling/' rel='bookmark' title='SKC++: Event Handling'>SKC++: Event Handling</a></li>
<li><a href='http://software-integrity.com/blog/2009/11/02/skc-message-passing-principles/' rel='bookmark' title='SKC++: Message-Passing Principles'>SKC++: Message-Passing Principles</a></li>
<li><a href='http://software-integrity.com/blog/2009/11/16/skc-sending-messages/' rel='bookmark' title='SKC++: Sending Messages'>SKC++: Sending Messages</a></li>
<li><a href='http://software-integrity.com/blog/2009/12/02/skc-mutual-exclusion/' rel='bookmark' title='SKC++: Mutual Exclusion'>SKC++: Mutual Exclusion</a></li>
</ol>]]></description>
		<wfw:commentRss>http://software-integrity.com/blog/2010/01/07/skc-no-semaphores/feed/</wfw:commentRss>
		<slash:comments>12</slash:comments>
		</item>
		<item>
		<title>SKC++: Interrupt handling</title>
		<link>http://software-integrity.com/blog/2009/12/15/skc-interrupt-handling/</link>
		<comments>http://software-integrity.com/blog/2009/12/15/skc-interrupt-handling/#comments</comments>
		<pubDate>Tue, 15 Dec 2009 20:26:51 +0000</pubDate>
		<dc:creator>Peter Bushell</dc:creator>
				<category><![CDATA[Interrupts]]></category>
		<category><![CDATA[Projects]]></category>
		<category><![CDATA[RTOS]]></category>
		<category><![CDATA[SKC++]]></category>

		<guid isPermaLink="false">http://software-integrity.com/blog/?p=446</guid>
		<description><![CDATA[When it comes to interrupts, SKC++&#8217;s guiding principle is &#8220;minimum interference&#8221;. Some kernels require that interrupts be processed internally, the internal Interrupt Service Routine (ISR) calling out to an ordinary user function, sometimes also called an ISR, confusingly. Some others let you code the ISR yourself but impose restrictions on how you do it. SKC++ [...]
Related posts:<ol>
<li><a href='http://software-integrity.com/blog/2009/10/14/skc-event-handling/' rel='bookmark' title='SKC++: Event Handling'>SKC++: Event Handling</a></li>
<li><a href='http://software-integrity.com/blog/2009/12/02/skc-mutual-exclusion/' rel='bookmark' title='SKC++: Mutual Exclusion'>SKC++: Mutual Exclusion</a></li>
<li><a href='http://software-integrity.com/blog/2010/01/07/skc-no-semaphores/' rel='bookmark' title='SKC++: No semaphores!'>SKC++: No semaphores!</a></li>
</ol>]]></description>
		<wfw:commentRss>http://software-integrity.com/blog/2009/12/15/skc-interrupt-handling/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>SKC++: Mutual Exclusion</title>
		<link>http://software-integrity.com/blog/2009/12/02/skc-mutual-exclusion/</link>
		<comments>http://software-integrity.com/blog/2009/12/02/skc-mutual-exclusion/#comments</comments>
		<pubDate>Wed, 02 Dec 2009 21:08:27 +0000</pubDate>
		<dc:creator>Peter Bushell</dc:creator>
				<category><![CDATA[Mutual Exclusion]]></category>
		<category><![CDATA[Projects]]></category>
		<category><![CDATA[RTOS]]></category>
		<category><![CDATA[SKC++]]></category>

		<guid isPermaLink="false">http://software-integrity.com/blog/?p=438</guid>
		<description><![CDATA[Just a short article today as SKC++&#8217;s mutual exclusion facilities follow a familiar pattern: It seemed like a good idea to provide another abstract interface as there can, in principle, be several kinds of mutex. The one I chose as &#8220;standard&#8221; for SKC++ is the priority-inheritance mutex. Fortunately, I don&#8217;t have to explain the ins [...]
No related posts.]]></description>
		<wfw:commentRss>http://software-integrity.com/blog/2009/12/02/skc-mutual-exclusion/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>SKC++: Receiving messages</title>
		<link>http://software-integrity.com/blog/2009/11/19/skc-receiving-messages/</link>
		<comments>http://software-integrity.com/blog/2009/11/19/skc-receiving-messages/#comments</comments>
		<pubDate>Thu, 19 Nov 2009 15:46:35 +0000</pubDate>
		<dc:creator>Peter Bushell</dc:creator>
				<category><![CDATA[Message-Passing]]></category>
		<category><![CDATA[Projects]]></category>
		<category><![CDATA[RTOS]]></category>
		<category><![CDATA[SKC++]]></category>

		<guid isPermaLink="false">http://software-integrity.com/blog/?p=408</guid>
		<description><![CDATA[Although I separated the ideas of posting an untrammelled event, using post, and sending a message (which also posts an event), using send, this is not such a good idea for receiving messages. One of the key things about an SKC++ task is that it should be able to wait at a single point in [...]
Related posts:<ol>
<li><a href='http://software-integrity.com/blog/2009/11/16/skc-sending-messages/' rel='bookmark' title='SKC++: Sending Messages'>SKC++: Sending Messages</a></li>
<li><a href='http://software-integrity.com/blog/2009/11/02/skc-message-passing-principles/' rel='bookmark' title='SKC++: Message-Passing Principles'>SKC++: Message-Passing Principles</a></li>
<li><a href='http://software-integrity.com/blog/2009/11/18/skc-change-to-send-function/' rel='bookmark' title='SKC++: Change to &#8220;send&#8221; function'>SKC++: Change to &#8220;send&#8221; function</a></li>
<li><a href='http://software-integrity.com/blog/2009/10/19/skc-tasks-and-timers/' rel='bookmark' title='SKC++: Tasks and Timers'>SKC++: Tasks and Timers</a></li>
<li><a href='http://software-integrity.com/blog/2010/01/07/skc-no-semaphores/' rel='bookmark' title='SKC++: No semaphores!'>SKC++: No semaphores!</a></li>
</ol>]]></description>
		<wfw:commentRss>http://software-integrity.com/blog/2009/11/19/skc-receiving-messages/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>SKC++: Change to &#8220;send&#8221; function</title>
		<link>http://software-integrity.com/blog/2009/11/18/skc-change-to-send-function/</link>
		<comments>http://software-integrity.com/blog/2009/11/18/skc-change-to-send-function/#comments</comments>
		<pubDate>Wed, 18 Nov 2009 11:17:03 +0000</pubDate>
		<dc:creator>Peter Bushell</dc:creator>
				<category><![CDATA[Message-Passing]]></category>
		<category><![CDATA[Projects]]></category>
		<category><![CDATA[RTOS]]></category>
		<category><![CDATA[SKC++]]></category>

		<guid isPermaLink="false">http://software-integrity.com/blog/?p=403</guid>
		<description><![CDATA[I have simplified the prototype for send in order to make its use a little easier and also to improve the efficiency of the implementation. Here is the new prototype: void send(MessagePtr&#38; pMessage, const Event event); The function no longer returns  a MessagePtr, and the concept of using a &#8220;system message&#8221;, in some circumstances, has [...]
Related posts:<ol>
<li><a href='http://software-integrity.com/blog/2009/11/16/skc-sending-messages/' rel='bookmark' title='SKC++: Sending Messages'>SKC++: Sending Messages</a></li>
<li><a href='http://software-integrity.com/blog/2009/11/19/skc-receiving-messages/' rel='bookmark' title='SKC++: Receiving messages'>SKC++: Receiving messages</a></li>
<li><a href='http://software-integrity.com/blog/2009/11/05/skc-message-passing-classes/' rel='bookmark' title='SKC++: Message-Passing Classes'>SKC++: Message-Passing Classes</a></li>
<li><a href='http://software-integrity.com/blog/2009/11/02/skc-message-passing-principles/' rel='bookmark' title='SKC++: Message-Passing Principles'>SKC++: Message-Passing Principles</a></li>
<li><a href='http://software-integrity.com/blog/2009/11/04/skc-message-passing-uses/' rel='bookmark' title='SKC++: Message-Passing Uses'>SKC++: Message-Passing Uses</a></li>
</ol>]]></description>
		<wfw:commentRss>http://software-integrity.com/blog/2009/11/18/skc-change-to-send-function/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>SKC++: Sending Messages</title>
		<link>http://software-integrity.com/blog/2009/11/16/skc-sending-messages/</link>
		<comments>http://software-integrity.com/blog/2009/11/16/skc-sending-messages/#comments</comments>
		<pubDate>Mon, 16 Nov 2009 12:26:33 +0000</pubDate>
		<dc:creator>Peter Bushell</dc:creator>
				<category><![CDATA[Message-Passing]]></category>
		<category><![CDATA[Projects]]></category>
		<category><![CDATA[RTOS]]></category>
		<category><![CDATA[SKC++]]></category>

		<guid isPermaLink="false">http://software-integrity.com/blog/?p=382</guid>
		<description><![CDATA[This is a relatively short article, as the sending of messages from one task to another is straightforward. I decided to defer its counterpart, &#8220;Receiving Messages&#8221;, until next time because there are several things to consider there, making the subject worthy of an article of its own. A while ago, I stated that messages can [...]
Related posts:<ol>
<li><a href='http://software-integrity.com/blog/2009/11/19/skc-receiving-messages/' rel='bookmark' title='SKC++: Receiving messages'>SKC++: Receiving messages</a></li>
<li><a href='http://software-integrity.com/blog/2009/11/18/skc-change-to-send-function/' rel='bookmark' title='SKC++: Change to &#8220;send&#8221; function'>SKC++: Change to &#8220;send&#8221; function</a></li>
<li><a href='http://software-integrity.com/blog/2009/11/05/skc-message-passing-classes/' rel='bookmark' title='SKC++: Message-Passing Classes'>SKC++: Message-Passing Classes</a></li>
<li><a href='http://software-integrity.com/blog/2009/11/02/skc-message-passing-principles/' rel='bookmark' title='SKC++: Message-Passing Principles'>SKC++: Message-Passing Principles</a></li>
<li><a href='http://software-integrity.com/blog/2009/11/04/skc-message-passing-uses/' rel='bookmark' title='SKC++: Message-Passing Uses'>SKC++: Message-Passing Uses</a></li>
</ol>]]></description>
		<wfw:commentRss>http://software-integrity.com/blog/2009/11/16/skc-sending-messages/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>SKC++: Message-Passing Classes</title>
		<link>http://software-integrity.com/blog/2009/11/05/skc-message-passing-classes/</link>
		<comments>http://software-integrity.com/blog/2009/11/05/skc-message-passing-classes/#comments</comments>
		<pubDate>Thu, 05 Nov 2009 16:40:40 +0000</pubDate>
		<dc:creator>Peter Bushell</dc:creator>
				<category><![CDATA[Message-Passing]]></category>
		<category><![CDATA[Projects]]></category>
		<category><![CDATA[RTOS]]></category>
		<category><![CDATA[SKC++]]></category>

		<guid isPermaLink="false">http://software-integrity.com/blog/?p=358</guid>
		<description><![CDATA[To avoid clutter, I haven&#8217;t shown the class methods. On this occasion, I&#8217;ll just describe the classes and their characteristics in the text. Message and aMessage The class aMessage, shown in green is some kind of message the application needs. The only rules for aMessage, as far as SKC++ is concerned, are: It must be [...]
Related posts:<ol>
<li><a href='http://software-integrity.com/blog/2009/11/02/skc-message-passing-principles/' rel='bookmark' title='SKC++: Message-Passing Principles'>SKC++: Message-Passing Principles</a></li>
<li><a href='http://software-integrity.com/blog/2009/11/04/skc-message-passing-uses/' rel='bookmark' title='SKC++: Message-Passing Uses'>SKC++: Message-Passing Uses</a></li>
<li><a href='http://software-integrity.com/blog/2009/09/30/skc-dynamic-memory-classes/' rel='bookmark' title='SKC++: Dynamic Memory Classes'>SKC++: Dynamic Memory Classes</a></li>
<li><a href='http://software-integrity.com/blog/2009/11/19/skc-receiving-messages/' rel='bookmark' title='SKC++: Receiving messages'>SKC++: Receiving messages</a></li>
<li><a href='http://software-integrity.com/blog/2009/11/16/skc-sending-messages/' rel='bookmark' title='SKC++: Sending Messages'>SKC++: Sending Messages</a></li>
</ol>]]></description>
		<wfw:commentRss>http://software-integrity.com/blog/2009/11/05/skc-message-passing-classes/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>SKC++: Message-Passing Uses</title>
		<link>http://software-integrity.com/blog/2009/11/04/skc-message-passing-uses/</link>
		<comments>http://software-integrity.com/blog/2009/11/04/skc-message-passing-uses/#comments</comments>
		<pubDate>Wed, 04 Nov 2009 16:29:18 +0000</pubDate>
		<dc:creator>Peter Bushell</dc:creator>
				<category><![CDATA[Message-Passing]]></category>
		<category><![CDATA[Projects]]></category>
		<category><![CDATA[RTOS]]></category>
		<category><![CDATA[SKC++]]></category>

		<guid isPermaLink="false">http://software-integrity.com/blog/?p=335</guid>
		<description><![CDATA[Before jumping into the design of the message-passing classes, it is as well to consider how the facility might be used in applications. I start with a common, nicely encapsulated but rather restricted kind of use&#8230; Local Message-Passing In this slightly abused UML activity diagram we see that the message is created in someFunction, which [...]
Related posts:<ol>
<li><a href='http://software-integrity.com/blog/2009/11/02/skc-message-passing-principles/' rel='bookmark' title='SKC++: Message-Passing Principles'>SKC++: Message-Passing Principles</a></li>
<li><a href='http://software-integrity.com/blog/2009/11/05/skc-message-passing-classes/' rel='bookmark' title='SKC++: Message-Passing Classes'>SKC++: Message-Passing Classes</a></li>
<li><a href='http://software-integrity.com/blog/2009/11/16/skc-sending-messages/' rel='bookmark' title='SKC++: Sending Messages'>SKC++: Sending Messages</a></li>
<li><a href='http://software-integrity.com/blog/2009/11/19/skc-receiving-messages/' rel='bookmark' title='SKC++: Receiving messages'>SKC++: Receiving messages</a></li>
<li><a href='http://software-integrity.com/blog/2009/11/18/skc-change-to-send-function/' rel='bookmark' title='SKC++: Change to &#8220;send&#8221; function'>SKC++: Change to &#8220;send&#8221; function</a></li>
</ol>]]></description>
		<wfw:commentRss>http://software-integrity.com/blog/2009/11/04/skc-message-passing-uses/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>SKC++: Message-Passing Principles</title>
		<link>http://software-integrity.com/blog/2009/11/02/skc-message-passing-principles/</link>
		<comments>http://software-integrity.com/blog/2009/11/02/skc-message-passing-principles/#comments</comments>
		<pubDate>Mon, 02 Nov 2009 16:07:04 +0000</pubDate>
		<dc:creator>Peter Bushell</dc:creator>
				<category><![CDATA[Message-Passing]]></category>
		<category><![CDATA[Projects]]></category>
		<category><![CDATA[RTOS]]></category>
		<category><![CDATA[SKC++]]></category>

		<guid isPermaLink="false">http://software-integrity.com/blog/?p=328</guid>
		<description><![CDATA[Message-passing is used, in an RTOS-based system, to provide a safe way of transferring data from one context to another or, in other words, from task to task. What is safe, though, is not always efficient and vice versa. To copy or not to copy? Some systems use copying to transfer data across the context [...]
Related posts:<ol>
<li><a href='http://software-integrity.com/blog/2009/11/04/skc-message-passing-uses/' rel='bookmark' title='SKC++: Message-Passing Uses'>SKC++: Message-Passing Uses</a></li>
<li><a href='http://software-integrity.com/blog/2009/11/05/skc-message-passing-classes/' rel='bookmark' title='SKC++: Message-Passing Classes'>SKC++: Message-Passing Classes</a></li>
<li><a href='http://software-integrity.com/blog/2009/11/16/skc-sending-messages/' rel='bookmark' title='SKC++: Sending Messages'>SKC++: Sending Messages</a></li>
<li><a href='http://software-integrity.com/blog/2009/11/19/skc-receiving-messages/' rel='bookmark' title='SKC++: Receiving messages'>SKC++: Receiving messages</a></li>
<li><a href='http://software-integrity.com/blog/2009/10/27/skc-pause-for-thought/' rel='bookmark' title='SKC++: Pause for Thought'>SKC++: Pause for Thought</a></li>
</ol>]]></description>
		<wfw:commentRss>http://software-integrity.com/blog/2009/11/02/skc-message-passing-principles/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>SKC++: Pause for Thought</title>
		<link>http://software-integrity.com/blog/2009/10/27/skc-pause-for-thought/</link>
		<comments>http://software-integrity.com/blog/2009/10/27/skc-pause-for-thought/#comments</comments>
		<pubDate>Tue, 27 Oct 2009 09:46:59 +0000</pubDate>
		<dc:creator>Peter Bushell</dc:creator>
				<category><![CDATA[Multitasking]]></category>
		<category><![CDATA[Projects]]></category>
		<category><![CDATA[RTOS]]></category>
		<category><![CDATA[SKC++]]></category>

		<guid isPermaLink="false">http://software-integrity.com/blog/?p=280</guid>
		<description><![CDATA[I&#8217;ve been looking over my SKC++ postings so far and have come to the conclusion that it&#8217;s time for a review. Also, before launching into the details of the kernel&#8217;s message-passing techniques, I need to show why message-passing is needed in the first place. I&#8217;ll start by presenting some thoughts on the tasking model. Encapsulation, [...]
Related posts:<ol>
<li><a href='http://software-integrity.com/blog/2009/10/06/skc-prototype-task-class/' rel='bookmark' title='SKC++: Prototype Task Class'>SKC++: Prototype Task Class</a></li>
<li><a href='http://software-integrity.com/blog/2009/10/14/skc-event-handling/' rel='bookmark' title='SKC++: Event Handling'>SKC++: Event Handling</a></li>
<li><a href='http://software-integrity.com/blog/2009/11/02/skc-message-passing-principles/' rel='bookmark' title='SKC++: Message-Passing Principles'>SKC++: Message-Passing Principles</a></li>
<li><a href='http://software-integrity.com/blog/2009/10/19/skc-tasks-and-timers/' rel='bookmark' title='SKC++: Tasks and Timers'>SKC++: Tasks and Timers</a></li>
<li><a href='http://software-integrity.com/blog/2009/11/04/skc-message-passing-uses/' rel='bookmark' title='SKC++: Message-Passing Uses'>SKC++: Message-Passing Uses</a></li>
</ol>]]></description>
		<wfw:commentRss>http://software-integrity.com/blog/2009/10/27/skc-pause-for-thought/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>SKC++: Tasks and Timers</title>
		<link>http://software-integrity.com/blog/2009/10/19/skc-tasks-and-timers/</link>
		<comments>http://software-integrity.com/blog/2009/10/19/skc-tasks-and-timers/#comments</comments>
		<pubDate>Mon, 19 Oct 2009 17:43:14 +0000</pubDate>
		<dc:creator>Peter Bushell</dc:creator>
				<category><![CDATA[Multitasking]]></category>
		<category><![CDATA[Projects]]></category>
		<category><![CDATA[RTOS]]></category>
		<category><![CDATA[SKC++]]></category>

		<guid isPermaLink="false">http://software-integrity.com/blog/?p=252</guid>
		<description><![CDATA[Just possibly, you may have been wondering why Task::wait does not include a timeout parameter. The answer is that it does not need to because a timeout is itself an event, so this can be waited for along with whatever event might be timed out. SKC++ has general-purpose timers which can be used not only [...]
Related posts:<ol>
<li><a href='http://software-integrity.com/blog/2009/10/14/skc-event-handling/' rel='bookmark' title='SKC++: Event Handling'>SKC++: Event Handling</a></li>
<li><a href='http://software-integrity.com/blog/2009/10/27/skc-pause-for-thought/' rel='bookmark' title='SKC++: Pause for Thought'>SKC++: Pause for Thought</a></li>
<li><a href='http://software-integrity.com/blog/2009/10/06/skc-prototype-task-class/' rel='bookmark' title='SKC++: Prototype Task Class'>SKC++: Prototype Task Class</a></li>
<li><a href='http://software-integrity.com/blog/2009/11/16/skc-sending-messages/' rel='bookmark' title='SKC++: Sending Messages'>SKC++: Sending Messages</a></li>
<li><a href='http://software-integrity.com/blog/2010/01/07/skc-no-semaphores/' rel='bookmark' title='SKC++: No semaphores!'>SKC++: No semaphores!</a></li>
</ol>]]></description>
		<wfw:commentRss>http://software-integrity.com/blog/2009/10/19/skc-tasks-and-timers/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>SKC++: Event Handling</title>
		<link>http://software-integrity.com/blog/2009/10/14/skc-event-handling/</link>
		<comments>http://software-integrity.com/blog/2009/10/14/skc-event-handling/#comments</comments>
		<pubDate>Wed, 14 Oct 2009 14:55:11 +0000</pubDate>
		<dc:creator>Peter Bushell</dc:creator>
				<category><![CDATA[Multitasking]]></category>
		<category><![CDATA[Projects]]></category>
		<category><![CDATA[RTOS]]></category>
		<category><![CDATA[SKC++]]></category>

		<guid isPermaLink="false">http://software-integrity.com/blog/?p=234</guid>
		<description><![CDATA[Systems running a pre-emptive kernel are essentially event-driven. Primary events are things which happen outside the software system, in the real world. These are usually communicated to the software via Interrupt Service Routines (ISRs) which are pre-emptively &#8220;called&#8221; by the hardware interrupt mechanism of the processor. Our kernel becomes aware of the event if and [...]
Related posts:<ol>
<li><a href='http://software-integrity.com/blog/2009/12/15/skc-interrupt-handling/' rel='bookmark' title='SKC++: Interrupt handling'>SKC++: Interrupt handling</a></li>
<li><a href='http://software-integrity.com/blog/2009/10/19/skc-tasks-and-timers/' rel='bookmark' title='SKC++: Tasks and Timers'>SKC++: Tasks and Timers</a></li>
<li><a href='http://software-integrity.com/blog/2010/01/07/skc-no-semaphores/' rel='bookmark' title='SKC++: No semaphores!'>SKC++: No semaphores!</a></li>
<li><a href='http://software-integrity.com/blog/2009/10/06/skc-prototype-task-class/' rel='bookmark' title='SKC++: Prototype Task Class'>SKC++: Prototype Task Class</a></li>
<li><a href='http://software-integrity.com/blog/2009/11/02/skc-message-passing-principles/' rel='bookmark' title='SKC++: Message-Passing Principles'>SKC++: Message-Passing Principles</a></li>
</ol>]]></description>
		<wfw:commentRss>http://software-integrity.com/blog/2009/10/14/skc-event-handling/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>The meaning of ESC</title>
		<link>http://software-integrity.com/blog/2009/10/09/the-meaning-of-esc/</link>
		<comments>http://software-integrity.com/blog/2009/10/09/the-meaning-of-esc/#comments</comments>
		<pubDate>Fri, 09 Oct 2009 19:45:25 +0000</pubDate>
		<dc:creator>Peter Bushell</dc:creator>
				<category><![CDATA[No Category]]></category>

		<guid isPermaLink="false">http://software-integrity.com/blog/?p=223</guid>
		<description><![CDATA[Some wistful thinking, as a break from blogging about SKC++. I spent the last two days at the ESC in Farnborough, UK. Would that be: Embedded Systems Conference, or Embedded System Complication, or Embedded System Confusion? Or all three? I went to 1, experienced 2 and came away suffering from 3. Like the PC industry, [...]
No related posts.]]></description>
		<wfw:commentRss>http://software-integrity.com/blog/2009/10/09/the-meaning-of-esc/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>SKC++: Prototype Task Class</title>
		<link>http://software-integrity.com/blog/2009/10/06/skc-prototype-task-class/</link>
		<comments>http://software-integrity.com/blog/2009/10/06/skc-prototype-task-class/#comments</comments>
		<pubDate>Tue, 06 Oct 2009 17:47:13 +0000</pubDate>
		<dc:creator>Peter Bushell</dc:creator>
				<category><![CDATA[Multitasking]]></category>
		<category><![CDATA[Projects]]></category>
		<category><![CDATA[RTOS]]></category>
		<category><![CDATA[SKC++]]></category>

		<guid isPermaLink="false">http://software-integrity.com/blog/?p=155</guid>
		<description><![CDATA[Today&#8217;s post discusses the basic structure and characteristics of an SKC++ task. Here is a picture of the class, together with a skeletal but updated version of the Pooled class, from which Task inherits: I emphasise that this diagram displays only the features required to show how Task is structured and set up for use [...]
Related posts:<ol>
<li><a href='http://software-integrity.com/blog/2009/10/14/skc-event-handling/' rel='bookmark' title='SKC++: Event Handling'>SKC++: Event Handling</a></li>
<li><a href='http://software-integrity.com/blog/2009/10/19/skc-tasks-and-timers/' rel='bookmark' title='SKC++: Tasks and Timers'>SKC++: Tasks and Timers</a></li>
<li><a href='http://software-integrity.com/blog/2009/10/27/skc-pause-for-thought/' rel='bookmark' title='SKC++: Pause for Thought'>SKC++: Pause for Thought</a></li>
<li><a href='http://software-integrity.com/blog/2009/11/04/skc-message-passing-uses/' rel='bookmark' title='SKC++: Message-Passing Uses'>SKC++: Message-Passing Uses</a></li>
</ol>]]></description>
		<wfw:commentRss>http://software-integrity.com/blog/2009/10/06/skc-prototype-task-class/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Tasks or Threads: what&#8217;s in a name?</title>
		<link>http://software-integrity.com/blog/2009/10/02/tasks-or-threads-whats-in-a-name/</link>
		<comments>http://software-integrity.com/blog/2009/10/02/tasks-or-threads-whats-in-a-name/#comments</comments>
		<pubDate>Fri, 02 Oct 2009 17:17:27 +0000</pubDate>
		<dc:creator>Peter Bushell</dc:creator>
				<category><![CDATA[Multitasking]]></category>
		<category><![CDATA[RTOS]]></category>

		<guid isPermaLink="false">http://software-integrity.com/blog/?p=181</guid>
		<description><![CDATA[Having spent almost my entire career in embedded and real-time software, I have become familiar with the term &#8220;task&#8221; to describe what might be called a &#8220;unit of concurrency&#8221; in a software system. Many people now use the term &#8220;thread&#8221; instead. Is there any difference? Yes and No. Here&#8217;s my take on it: Threads (and [...]
No related posts.]]></description>
		<wfw:commentRss>http://software-integrity.com/blog/2009/10/02/tasks-or-threads-whats-in-a-name/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
	</channel>
</rss>

