<?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>There Is NO Box &#187; c programming</title>
	<atom:link href="http://tinobox.com/wordpress/category/c-programming/feed/" rel="self" type="application/rss+xml" />
	<link>http://tinobox.com/wordpress</link>
	<description>Odds and ends of internet entrepreneurship—A Technical Diary</description>
	<lastBuildDate>Fri, 25 Nov 2011 22:08:48 +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>Object Oriented C: Single inheritance Part II</title>
		<link>http://tinobox.com/wordpress/c-programming/object-oriented-single-inheritance-part-ii/</link>
		<comments>http://tinobox.com/wordpress/c-programming/object-oriented-single-inheritance-part-ii/#comments</comments>
		<pubDate>Mon, 07 Mar 2011 23:15:00 +0000</pubDate>
		<dc:creator>David M. Doolin, PhD</dc:creator>
				<category><![CDATA[c programming]]></category>
		<category><![CDATA[CPP macro]]></category>
		<category><![CDATA[object-oriented c]]></category>
		<category><![CDATA[OOC]]></category>
		<category><![CDATA[Single inheritance]]></category>

		<guid isPermaLink="false">http://tinobox.com/wordpress/?p=5432</guid>
		<description><![CDATA[Here&#8217;s another installment on Object Oriented C programming. This time, we&#8217;re going to take a look at how inheritance allows you to simulate a generic function courtesy of the C preprocessor. If you have ever wondered how those spiffy objects in other programming languages always get &#8220;printed,&#8221; here&#8217;s one way to do it. First, let&#8217;s [...]<p>Post from: <a href="http://tinobox.com/wordpress">There Is NO Box</a><br/><br/><a href="http://tinobox.com/wordpress/c-programming/object-oriented-single-inheritance-part-ii/">Object Oriented C: Single inheritance Part II</a></p>
]]></description>
		<wfw:commentRss>http://tinobox.com/wordpress/c-programming/object-oriented-single-inheritance-part-ii/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Single Inheritance In C Programming Language I: Nesting structures</title>
		<link>http://tinobox.com/wordpress/c-programming/single-inheritance-programming-language-nesting-structures/</link>
		<comments>http://tinobox.com/wordpress/c-programming/single-inheritance-programming-language-nesting-structures/#comments</comments>
		<pubDate>Sat, 05 Mar 2011 16:11:12 +0000</pubDate>
		<dc:creator>David M. Doolin, PhD</dc:creator>
				<category><![CDATA[c programming]]></category>
		<category><![CDATA[Code design]]></category>
		<category><![CDATA[OOC]]></category>
		<category><![CDATA[Single inheritance]]></category>

		<guid isPermaLink="false">http://tinobox.com/wordpress/?p=15</guid>
		<description><![CDATA[The C programming language lends itself well to single inheritance object-oriented schemes, provided a little care is taken in the class structure. Consider the following definition: 1 2 3 typedef struct _object &#123; int foo; &#125; Object; 1 2 3 4 typedef struct _thing &#123; Object o; double bar; &#125; Thing; Right here, I know [...]<p>Post from: <a href="http://tinobox.com/wordpress">There Is NO Box</a><br/><br/><a href="http://tinobox.com/wordpress/c-programming/single-inheritance-programming-language-nesting-structures/">Single Inheritance In C Programming Language I: Nesting structures</a></p>
]]></description>
		<wfw:commentRss>http://tinobox.com/wordpress/c-programming/single-inheritance-programming-language-nesting-structures/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Simple Object Oriented Unit Testing For C Programming</title>
		<link>http://tinobox.com/wordpress/c-programming/simple-object-oriented-unit-testing-programming/</link>
		<comments>http://tinobox.com/wordpress/c-programming/simple-object-oriented-unit-testing-programming/#comments</comments>
		<pubDate>Tue, 04 Jan 2011 00:46:58 +0000</pubDate>
		<dc:creator>David M. Doolin, PhD</dc:creator>
				<category><![CDATA[c programming]]></category>
		<category><![CDATA[OOC]]></category>
		<category><![CDATA[programming]]></category>
		<category><![CDATA[Project management]]></category>
		<category><![CDATA[Unit testing]]></category>

		<guid isPermaLink="false">http://tinobox.com/wordpress/?p=1403</guid>
		<description><![CDATA[Remember that giant blast of wind a few months ago? The wind that launched all my cool plants down the stairs? Well, here&#8217;s a picture of the re-potted collection. That&#8217;s about half of them, the other half are still languishing. Crassulae are tough as nails. I may re-pot the remaining&#8230; but these need to be [...]<p>Post from: <a href="http://tinobox.com/wordpress">There Is NO Box</a><br/><br/><a href="http://tinobox.com/wordpress/c-programming/simple-object-oriented-unit-testing-programming/">Simple Object Oriented Unit Testing For C Programming</a></p>
]]></description>
		<wfw:commentRss>http://tinobox.com/wordpress/c-programming/simple-object-oriented-unit-testing-programming/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>How To Hide A Struct Member in the C Programming Language</title>
		<link>http://tinobox.com/wordpress/c-programming/how-to-hide-a-struct-member-in-the-c-programming-language/</link>
		<comments>http://tinobox.com/wordpress/c-programming/how-to-hide-a-struct-member-in-the-c-programming-language/#comments</comments>
		<pubDate>Mon, 01 Jun 2009 16:54:55 +0000</pubDate>
		<dc:creator>David M. Doolin, PhD</dc:creator>
				<category><![CDATA[c programming]]></category>
		<category><![CDATA[Data hiding]]></category>
		<category><![CDATA[Encapsulation]]></category>
		<category><![CDATA[OOC]]></category>
		<category><![CDATA[Struct]]></category>
		<category><![CDATA[Unix]]></category>

		<guid isPermaLink="false">http://tinobox.com/wordpress/?p=2132</guid>
		<description><![CDATA[Update: A friend pointed out a typo, which is now fixed in both the article and the code. Hiding a struct member in C is easy using incomplete types. There&#8217;s two ways to do it: Hide the whole struct definition Hide a single member of a struct Either way requires using a typedef to define [...]<p>Post from: <a href="http://tinobox.com/wordpress">There Is NO Box</a><br/><br/><a href="http://tinobox.com/wordpress/c-programming/how-to-hide-a-struct-member-in-the-c-programming-language/">How To Hide A Struct Member in the C Programming Language</a></p>
]]></description>
		<wfw:commentRss>http://tinobox.com/wordpress/c-programming/how-to-hide-a-struct-member-in-the-c-programming-language/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>gcc Linking Errors  &#8212; Simpler than you think to fix</title>
		<link>http://tinobox.com/wordpress/c-programming/gcc-linking-errors-simpler-than-you-think-to-fix/</link>
		<comments>http://tinobox.com/wordpress/c-programming/gcc-linking-errors-simpler-than-you-think-to-fix/#comments</comments>
		<pubDate>Fri, 24 Apr 2009 02:32:40 +0000</pubDate>
		<dc:creator>David M. Doolin, PhD</dc:creator>
				<category><![CDATA[c programming]]></category>
		<category><![CDATA[Cooper Square Hotel]]></category>
		<category><![CDATA[Fried chicken]]></category>
		<category><![CDATA[Link error]]></category>
		<category><![CDATA[Unix]]></category>

		<guid isPermaLink="false">http://tinobox.com/wordpress/?p=1474</guid>
		<description><![CDATA[I&#8217;m sitting in the Cooper Square Hotel in Manhattan (long story), working on a nice little article on fast, small, simple unit testing, and looking south at downtown. I can see the cables and towers of the Williamsburg, Manhattan and Brooklyn Bridges. Cooper Square is where Bowery meets East Village. It’s nice. Think “Mission Hipster” [...]<p>Post from: <a href="http://tinobox.com/wordpress">There Is NO Box</a><br/><br/><a href="http://tinobox.com/wordpress/c-programming/gcc-linking-errors-simpler-than-you-think-to-fix/">gcc Linking Errors  &#8212; Simpler than you think to fix</a></p>
]]></description>
		<wfw:commentRss>http://tinobox.com/wordpress/c-programming/gcc-linking-errors-simpler-than-you-think-to-fix/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>LINK : fatal error LNK1181: cannot open input file &#8216;C:\Program.obj&#8217;</title>
		<link>http://tinobox.com/wordpress/c-programming/link-fatal-error-lnk1181-cannot-open-input-file-cprogramobj/</link>
		<comments>http://tinobox.com/wordpress/c-programming/link-fatal-error-lnk1181-cannot-open-input-file-cprogramobj/#comments</comments>
		<pubDate>Fri, 20 Mar 2009 20:55:15 +0000</pubDate>
		<dc:creator>David M. Doolin, PhD</dc:creator>
				<category><![CDATA[c programming]]></category>
		<category><![CDATA[kalanchoe]]></category>
		<category><![CDATA[Linker errors]]></category>
		<category><![CDATA[LNK1181]]></category>
		<category><![CDATA[plants]]></category>
		<category><![CDATA[qmake]]></category>
		<category><![CDATA[sedum]]></category>
		<category><![CDATA[VC++]]></category>

		<guid isPermaLink="false">http://tinobox.com/wordpress/?p=1062</guid>
		<description><![CDATA[I&#8217;m working on a HUGE article titled something like &#8220;More VC++ Compiler &#038; Linking Errors, with Real English Explanations&#8221; and it&#8217;s getting totally out of hand. Really long. And I need to go back through most of the article and make one more check (triple check) to make sure all the information is correct. Since [...]<p>Post from: <a href="http://tinobox.com/wordpress">There Is NO Box</a><br/><br/><a href="http://tinobox.com/wordpress/c-programming/link-fatal-error-lnk1181-cannot-open-input-file-cprogramobj/">LINK : fatal error LNK1181: cannot open input file &#8216;C:\Program.obj&#8217;</a></p>
]]></description>
		<wfw:commentRss>http://tinobox.com/wordpress/c-programming/link-fatal-error-lnk1181-cannot-open-input-file-cprogramobj/feed/</wfw:commentRss>
		<slash:comments>8</slash:comments>
		</item>
		<item>
		<title>C/C++ Naming conventions (Part II)</title>
		<link>http://tinobox.com/wordpress/c-programming/cc-naming-conventions-part-ii/</link>
		<comments>http://tinobox.com/wordpress/c-programming/cc-naming-conventions-part-ii/#comments</comments>
		<pubDate>Wed, 04 Feb 2009 17:25:15 +0000</pubDate>
		<dc:creator>David M. Doolin, PhD</dc:creator>
				<category><![CDATA[c programming]]></category>
		<category><![CDATA[coding]]></category>
		<category><![CDATA[Code design]]></category>
		<category><![CDATA[Unix]]></category>

		<guid isPermaLink="false">http://tinobox.com/wordpress/?p=58</guid>
		<description><![CDATA[I estimate about half the code I have reverse engineered has inconsistent naming conventions. Actually, nearly all code I have ever reverse engineered (and most of the code I have written) has some naming inconsistency. At issue is grossly inconsistent naming. Consistent naming provides the following benefits: The sames kinds of objects, entities, types will [...]<p>Post from: <a href="http://tinobox.com/wordpress">There Is NO Box</a><br/><br/><a href="http://tinobox.com/wordpress/c-programming/cc-naming-conventions-part-ii/">C/C++ Naming conventions (Part II)</a></p>
]]></description>
		<wfw:commentRss>http://tinobox.com/wordpress/c-programming/cc-naming-conventions-part-ii/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Linking in Microsoft Visual Studio C++</title>
		<link>http://tinobox.com/wordpress/c-programming/linking-microsoft-visual-studio-c/</link>
		<comments>http://tinobox.com/wordpress/c-programming/linking-microsoft-visual-studio-c/#comments</comments>
		<pubDate>Thu, 22 Jan 2009 22:05:45 +0000</pubDate>
		<dc:creator>David M. Doolin, PhD</dc:creator>
				<category><![CDATA[c programming]]></category>
		<category><![CDATA[coding]]></category>

		<guid isPermaLink="false">http://tinobox.com/wordpress/?p=125</guid>
		<description><![CDATA[[Note: If you do NOT find what you were looking for in this article, please leave a comment. I'll update as necessary to keep the information accurate, useful and current.] Once upon a time, I was a graduate student at UC Berkeley, and spent a fair bit of time in the engineering library. I recall [...]<p>Post from: <a href="http://tinobox.com/wordpress">There Is NO Box</a><br/><br/><a href="http://tinobox.com/wordpress/c-programming/linking-microsoft-visual-studio-c/">Linking in Microsoft Visual Studio C++</a></p>
]]></description>
		<wfw:commentRss>http://tinobox.com/wordpress/c-programming/linking-microsoft-visual-studio-c/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>C/C++ Naming conventions (Part I)</title>
		<link>http://tinobox.com/wordpress/c-programming/naming-conventions-part-i/</link>
		<comments>http://tinobox.com/wordpress/c-programming/naming-conventions-part-i/#comments</comments>
		<pubDate>Tue, 19 Feb 2008 17:04:24 +0000</pubDate>
		<dc:creator>David M. Doolin, PhD</dc:creator>
				<category><![CDATA[c programming]]></category>
		<category><![CDATA[Code design]]></category>

		<guid isPermaLink="false">http://tinobox.com/wordpress/?p=16</guid>
		<description><![CDATA[Update [2/19/2008] The Use Case article on Wikipedia provides more support for verb-object form. Update [2/19/2009] Added some links for literate programming.     Naming conventions are an important and very practical aspect of literate programming. There are two fundamental requirements for naming conventions: Consistency of form, the &#8220;what it is&#8221; factor: Do the names [...]<p>Post from: <a href="http://tinobox.com/wordpress">There Is NO Box</a><br/><br/><a href="http://tinobox.com/wordpress/c-programming/naming-conventions-part-i/">C/C++ Naming conventions (Part I)</a></p>
]]></description>
		<wfw:commentRss>http://tinobox.com/wordpress/c-programming/naming-conventions-part-i/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Data Hiding in C: Programming Using Incomplete and Derived Types</title>
		<link>http://tinobox.com/wordpress/c-programming/incomplete-types-in-c-programming/</link>
		<comments>http://tinobox.com/wordpress/c-programming/incomplete-types-in-c-programming/#comments</comments>
		<pubDate>Tue, 19 Dec 2006 22:38:43 +0000</pubDate>
		<dc:creator>David M. Doolin, PhD</dc:creator>
				<category><![CDATA[c programming]]></category>
		<category><![CDATA[Code design]]></category>
		<category><![CDATA[OOC]]></category>
		<category><![CDATA[Software engineering]]></category>

		<guid isPermaLink="false">http://tinobox.com/wordpress/?p=3</guid>
		<description><![CDATA[>>>NOTE: You may want to start with a much simpler article in hiding member in structs. Data hiding and encapsulation in C is fairly easy using the notions of derived and incomplete types. A derived type is a user-defined type typically declared as members of a struct. An incomplete type is where the definition of [...]<p>Post from: <a href="http://tinobox.com/wordpress">There Is NO Box</a><br/><br/><a href="http://tinobox.com/wordpress/c-programming/incomplete-types-in-c-programming/">Data Hiding in C: Programming Using Incomplete and Derived Types</a></p>
]]></description>
		<wfw:commentRss>http://tinobox.com/wordpress/c-programming/incomplete-types-in-c-programming/feed/</wfw:commentRss>
		<slash:comments>8</slash:comments>
		</item>
		<item>
		<title>Why C and not C++?</title>
		<link>http://tinobox.com/wordpress/c-programming/why-c-and-not-c/</link>
		<comments>http://tinobox.com/wordpress/c-programming/why-c-and-not-c/#comments</comments>
		<pubDate>Sat, 09 Dec 2006 01:00:26 +0000</pubDate>
		<dc:creator>David M. Doolin, PhD</dc:creator>
				<category><![CDATA[c programming]]></category>
		<category><![CDATA[coding]]></category>

		<guid isPermaLink="false">http://tinobox.com/wordpress/?p=5</guid>
		<description><![CDATA[Why all this work coercing C into objected-oriented code, a form it wasn&#8217;t really designed for? This is a personal question spanning well over a decade of watching the C++ go from having no specification, to having a standard specfication not implemented anywhere, to having various parts of the standard implemented in various ways on [...]<p>Post from: <a href="http://tinobox.com/wordpress">There Is NO Box</a><br/><br/><a href="http://tinobox.com/wordpress/c-programming/why-c-and-not-c/">Why C and not C++?</a></p>
]]></description>
		<wfw:commentRss>http://tinobox.com/wordpress/c-programming/why-c-and-not-c/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

