<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/1.5.2" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Director: Compressing Lists from storage in text members</title>
	<link>http://blog.hanfordlemoore.com/2006/04/01/director-compressing-lists-from-storage-in-text-members</link>
	<description>User Interface , Art, Design, Games</description>
	<pubDate>Wed, 07 Jan 2009 02:09:48 +0000</pubDate>
	<generator>http://wordpress.org/?v=1.5.2</generator>

	<item>
 		<title>Comment on Director: Compressing Lists from storage in text members by: Hanford</title>
		<link>http://blog.hanfordlemoore.com/2006/04/01/director-compressing-lists-from-storage-in-text-members#comment-29448</link>
		<pubDate>Tue, 14 Nov 2006 11:50:52 +0000</pubDate>
		<guid>http://blog.hanfordlemoore.com/2006/04/01/director-compressing-lists-from-storage-in-text-members#comment-29448</guid>
					<description>I didn't mean Voids themselves are incorrect. 

Just that you need to plan for them; ignoring the fact that they can break the value() command will get you in trouble; so using this technique does indeed need you to design for them.</description>
		<content:encoded><![CDATA[	<p>I didn&#8217;t mean Voids themselves are incorrect.</p>
	<p>Just that you need to plan for them; ignoring the fact that they can break the value() command will get you in trouble; so using this technique does indeed need you to design for them.</p>
]]></content:encoded>
				</item>
	<item>
 		<title>Comment on Director: Compressing Lists from storage in text members by: rich</title>
		<link>http://blog.hanfordlemoore.com/2006/04/01/director-compressing-lists-from-storage-in-text-members#comment-29444</link>
		<pubDate>Tue, 14 Nov 2006 11:05:40 +0000</pubDate>
		<guid>http://blog.hanfordlemoore.com/2006/04/01/director-compressing-lists-from-storage-in-text-members#comment-29444</guid>
					<description>&amp;#62;&amp;#62;&amp;#62;&amp;#62;
Watch out though because Director’s value() command will choke on certain things, like the void token, and strings with returns in them. This is pretty easy to avoid if you design your program correctly, though.
&amp;#62;&amp;#62;&amp;#62;&amp;#62;

That's a rather brash claim, since voids don't imply an &quot;incorrect&quot; design. On the contrary, I'd say that writing your code under the assumtion you will never have a void value is at best error-prone, at worst lazy!

I do a similar thing to your space-saving, when saving lists like this and simply search and replace &quot;&quot; with &quot;void&quot;</description>
		<content:encoded><![CDATA[	<p>>>>><br />
Watch out though because Director&#8217;s value() command will choke on certain things, like the void token, and strings with returns in them. This is pretty easy to avoid if you design your program correctly, though.<br />
>>>></p>
	<p>That&#8217;s a rather brash claim, since voids don&#8217;t imply an &#8220;incorrect&#8221; design. On the contrary, I&#8217;d say that writing your code under the assumtion you will never have a void value is at best error-prone, at worst lazy!</p>
	<p>I do a similar thing to your space-saving, when saving lists like this and simply search and replace &#8220;&#8221; with &#8220;void&#8221; </p>
]]></content:encoded>
				</item>
</channel>
</rss>
