<?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: To CLOS or not to CLOS</title>
	<atom:link href="http://nklein.com/2009/06/to-clos-or-not-to-clos/feed/" rel="self" type="application/rss+xml" />
	<link>http://nklein.com/2009/06/to-clos-or-not-to-clos/</link>
	<description>software development and consulting</description>
	<lastBuildDate>Thu, 15 Jul 2010 11:51:39 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: pat</title>
		<link>http://nklein.com/2009/06/to-clos-or-not-to-clos/comment-page-1/#comment-171</link>
		<dc:creator>pat</dc:creator>
		<pubDate>Mon, 20 Jul 2009 14:48:46 +0000</pubDate>
		<guid isPermaLink="false">http://nklein.com/?p=624#comment-171</guid>
		<description>There are probably ways.  I would have to experiment quite a bit to get a way that I felt confident would work throughout.  I have since been reconsidering my stance on this.  I think I&#039;m still going to use classes and generic functions for things like cameras and meshes that I expect to get called only a couple of times per frame and use structs for things like facets and vertexes that will be referenced hundreds of thousands of times per frame.

I still haven&#039;t fully embraced Agile programming, but I have done enough fundamental changes to APIs in my time, that I&#039;m reasonably confident I can go back and retro-fit whatever I need to if some portion is weighting me down.
</description>
		<content:encoded><![CDATA[<p>There are probably ways.  I would have to experiment quite a bit to get a way that I felt confident would work throughout.  I have since been reconsidering my stance on this.  I think I&#8217;m still going to use classes and generic functions for things like cameras and meshes that I expect to get called only a couple of times per frame and use structs for things like facets and vertexes that will be referenced hundreds of thousands of times per frame.</p>
<p>I still haven&#8217;t fully embraced Agile programming, but I have done enough fundamental changes to APIs in my time, that I&#8217;m reasonably confident I can go back and retro-fit whatever I need to if some portion is weighting me down.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Grant Rettke</title>
		<link>http://nklein.com/2009/06/to-clos-or-not-to-clos/comment-page-1/#comment-169</link>
		<dc:creator>Grant Rettke</dc:creator>
		<pubDate>Mon, 20 Jul 2009 06:22:34 +0000</pubDate>
		<guid isPermaLink="false">http://nklein.com/?p=624#comment-169</guid>
		<description>Isn&#039;t there a way you can write your Lisp code so that even if you start out using structures you can make it very easy to migrate to objects later on?</description>
		<content:encoded><![CDATA[<p>Isn&#8217;t there a way you can write your Lisp code so that even if you start out using structures you can make it very easy to migrate to objects later on?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: pat</title>
		<link>http://nklein.com/2009/06/to-clos-or-not-to-clos/comment-page-1/#comment-132</link>
		<dc:creator>pat</dc:creator>
		<pubDate>Tue, 30 Jun 2009 01:12:59 +0000</pubDate>
		<guid isPermaLink="false">http://nklein.com/?p=624#comment-132</guid>
		<description>The structs are five times faster.  Certainly, both are fast enough for almost everything.  But, for realtime, interactive 3D stuff, there is enough going on that some of those 5x&#039;s could make a big difference.  Certainly, I don&#039;t want it to only be able to do 1/2 the resolution or a quarter of the polygons that the C++ version does if I can help it.

Yes, this falls in the &quot;premature optimization&quot; category.  But, it also falls in the &quot;easier to do now&quot; and &quot;just about as pretty&quot; and &quot;some of it will have thousands of accesses per frame&quot; categories.</description>
		<content:encoded><![CDATA[<p>The structs are five times faster.  Certainly, both are fast enough for almost everything.  But, for realtime, interactive 3D stuff, there is enough going on that some of those 5x&#8217;s could make a big difference.  Certainly, I don&#8217;t want it to only be able to do 1/2 the resolution or a quarter of the polygons that the C++ version does if I can help it.</p>
<p>Yes, this falls in the &#8220;premature optimization&#8221; category.  But, it also falls in the &#8220;easier to do now&#8221; and &#8220;just about as pretty&#8221; and &#8220;some of it will have thousands of accesses per frame&#8221; categories.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Zachary Beane</title>
		<link>http://nklein.com/2009/06/to-clos-or-not-to-clos/comment-page-1/#comment-131</link>
		<dc:creator>Zachary Beane</dc:creator>
		<pubDate>Tue, 30 Jun 2009 00:56:32 +0000</pubDate>
		<guid isPermaLink="false">http://nklein.com/?p=624#comment-131</guid>
		<description>So they&#039;re both so fast it doesn&#039;t matter which you use, but you&#039;re going to go with structs?</description>
		<content:encoded><![CDATA[<p>So they&#8217;re both so fast it doesn&#8217;t matter which you use, but you&#8217;re going to go with structs?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
