<?xml version="1.0" encoding="UTF-8"?>
<!-- generator="wordpress/wordpress-mu-1.2.5" -->
<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:slash="http://purl.org/rss/1.0/modules/slash/"
        xmlns:opencore="http://www.openplans.org/opencore"
	>

<channel>
	<title>LitCal</title>
	<link>http://www.cathnet.org/projects/litcal/blog</link>
	<description>Just another  weblog</description>
	<pubDate>Wed, 13 Oct 2010 13:51:39 +0000</pubDate>
	<generator>http://wordpress.org/?v=wordpress-mu-1.2.5</generator>
	<language>en</language>
			<item>
		<title>Super Quick Update</title>
		<link>http://www.cathnet.org/projects/litcal/blog/2010/10/13/super-quick-update/</link>
		<comments>http://www.cathnet.org/projects/litcal/blog/2010/10/13/super-quick-update/#comments</comments>
        	<slash:comments>0</slash:comments> 
		<pubDate>Wed, 13 Oct 2010 13:51:17 +0000</pubDate>
		<dc:creator>DJ</dc:creator>
                <opencore:userid>lutra</opencore:userid>
		
		<category><![CDATA[update]]></category>

		<guid isPermaLink="false">http://www.cathnet.org/projects/litcal/blog/2010/10/13/super-quick-update/</guid>
		<description><![CDATA[This is just a super quick update to inform anybody following that, yes, I am still alive and working on litCal.&#160; I&#8217;ve made some progress on filling out the API.&#160; At the moment, I&#8217;ve only really started on what I call the secular API, which relates to non-religious calendar functions.

&#160;I think the future direction that [...]]]></description>
			<content:encoded xml:base="http://www.cathnet.org/projects/litcal/blog/2010/10/13/super-quick-update/"><![CDATA[<p>This is just a super quick update to inform anybody following that, yes, I am still alive and working on litCal.&nbsp; I&#8217;ve made some progress on filling out the API.&nbsp; At the moment, I&#8217;ve only really started on what I call the secular API, which relates to non-religious calendar functions.
</p>
<p>&nbsp;I think the future direction that I plan on taking this is to create an ANSI C library that will act as a set of primitive calendar functions, such as basic computus and day of week calculations, and then use a C++ wrapper in a second library to provide a more integrated interface that has operator overloading, stores state (the date), produces output strings, etc..<br />
  </p>
]]></content:encoded>
			<wfw:commentRss>http://www.cathnet.org/projects/litcal/blog/2010/10/13/super-quick-update/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Status Update</title>
		<link>http://www.cathnet.org/projects/litcal/blog/2010/06/21/status-update/</link>
		<comments>http://www.cathnet.org/projects/litcal/blog/2010/06/21/status-update/#comments</comments>
        	<slash:comments>0</slash:comments> 
		<pubDate>Mon, 21 Jun 2010 21:43:29 +0000</pubDate>
		<dc:creator>DJ</dc:creator>
                <opencore:userid>lutra</opencore:userid>
		
		<category><![CDATA[update]]></category>

		<guid isPermaLink="false">http://www.cathnet.org/projects/litcal/blog/2010/06/21/status-update/</guid>
		<description><![CDATA[ Its been several months since I last worked on anything related to litCal, and I&#8217;m beginning to pick things back up again.&#160; I&#8217;m currently going through all of the code that I&#8217;ve written and am trying to remember what problems I was last working on before I took my little hiatus.

I don&#8217;t have an [...]]]></description>
			<content:encoded xml:base="http://www.cathnet.org/projects/litcal/blog/2010/06/21/status-update/"><![CDATA[<p> Its been several months since I last worked on anything related to litCal, and I&#8217;m beginning to pick things back up again.&nbsp; I&#8217;m currently going through all of the code that I&#8217;ve written and am trying to remember what problems I was last working on before I took my little hiatus.
</p>
<p>I don&#8217;t have an ETA of when I expect to be finished with at least a usable amount of code, but I&#8217;m hoping it won&#8217;t take too long.<br />
  </p>
]]></content:encoded>
			<wfw:commentRss>http://www.cathnet.org/projects/litcal/blog/2010/06/21/status-update/feed/</wfw:commentRss>
		</item>
		<item>
		<title>C versus C++</title>
		<link>http://www.cathnet.org/projects/litcal/blog/2010/02/17/c-versus-c/</link>
		<comments>http://www.cathnet.org/projects/litcal/blog/2010/02/17/c-versus-c/#comments</comments>
        	<slash:comments>0</slash:comments> 
		<pubDate>Wed, 17 Feb 2010 06:01:42 +0000</pubDate>
		<dc:creator>DJ</dc:creator>
                <opencore:userid>lutra</opencore:userid>
		
		<category><![CDATA[design decision]]></category>

		<guid isPermaLink="false">http://www.cathnet.org/projects/litcal/blog/2010/02/17/c-versus-c/</guid>
		<description><![CDATA[At the moment, I&#8217;m still chewing through some other technical details in my head before I start to move regarding working on the library.&#160; The question of language is not so much in the forefront of my thoughts, but it is something that I&#8217;m as of yet undecided on.

So, I&#8217;m writing this blog post to [...]]]></description>
			<content:encoded xml:base="http://www.cathnet.org/projects/litcal/blog/2010/02/17/c-versus-c/"><![CDATA[<p>At the moment, I&#8217;m still chewing through some other technical details in my head before I start to move regarding working on the library.&nbsp; The question of language is not so much in the forefront of my thoughts, but it is something that I&#8217;m as of yet undecided on.
</p>
<p>So, I&#8217;m writing this blog post to put out my thoughts regarding which language to choose from.&nbsp; If at all possible, I&#8217;d like comments, suggestions or any form of constructive criticism.<br />
  
</p>
<p>Firstly, though an easier and more powerful language (Python or Ruby perhaps) or a kewler language (Scheme comes to mind) would make the project a nicer one to work on, I want this library to be as generic and widely distributable as possible.&nbsp; In my mind, sticking to strictly ANSI C or C++ is probably the way to go.
</p>
<p>There are pros and cons to both languages in my mind.&nbsp; The following summarizes what I perceive to be important.&nbsp; Again, I&#8217;d like to reiterate that I&#8217;m open to others&#8217; input:
</p>
<h3><strong>ANSI C </strong><br />
  <br />
</h3>
<p><strong>Pros</strong>
</p>
<ul>
<li> <strong></strong>Easiest to make sure the code can compile in a wider variety of environments.</li>
<li>Along with C++, C is the Lingua Franca of application programming languages.&nbsp; And what&#8217;s more Catholic, than to use the Lingua Franca (think, Jerome&#8217;s Vulgate, the DRC&#8230;even the LXX for the early Christians.)</li>
<li>Unless I&#8217;m mistaken, which I could easily be, language bindings are easier to make.<br />
   </li>
</ul>
<p><strong>Cons</strong>
</p>
<ul>
<li>&nbsp;People don&#8217;t really like working in &#8216;plain old C.&#8217;&nbsp; There are too many nice features that would be missing, such as operator overloading, virtual methods, etc&#8230;</li>
<li>If I end up doing any sort of dynamic memory allocation for anything, does the end user really want to have to use functions to instantiate or clean up my mess?<br />
   </li>
</ul>
<h3><strong>C++ </strong><br />
</h3>
<p><strong>Pros</strong>
</p>
<ul>
<li> Still fairly easy to make code that can compile in the odder corners of the world.</li>
<li> Operator overloading means being able to do simple math with the objects such as adding or subtracting dates.</li>
<li>Can write code to clean up any data structures that may end up being created.</li>
</ul>
<ul>
<li>Complicated operations can more easily take place behind the scenes.</li>
</ul>
<p><strong>Cons</strong>
</p>
<ul>
<li> <strong></strong>Believe it or not, C++ is not as portable as one might think.&nbsp; Of course, I&#8217;ve worked in quite a few strange computing environments in my professional career, most of which will probably never see this library.</li>
<li>Though I don&#8217;t have much experience binding to other libraries, from what I can tell, C++ can be a bit of extra work when binding to languages such as Python or Free Pascal.</li>
</ul>
<p>&nbsp;</p>
]]></content:encoded>
			<wfw:commentRss>http://www.cathnet.org/projects/litcal/blog/2010/02/17/c-versus-c/feed/</wfw:commentRss>
		</item>
	</channel>
</rss>

