<?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: Plotting in Lisp, Part III</title>
	<atom:link href="http://www.nonperiodic.net/blog/2005/07/18/plotting-in-lisp-part-iii/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.nonperiodic.net/blog/2005/07/18/plotting-in-lisp-part-iii/</link>
	<description>Nonperiodic Central Trajectory</description>
	<lastBuildDate>Wed, 10 Jun 2009 09:47:09 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Robert Goldman</title>
		<link>http://www.nonperiodic.net/blog/2005/07/18/plotting-in-lisp-part-iii/comment-page-1/#comment-3146</link>
		<dc:creator>Robert Goldman</dc:creator>
		<pubDate>Wed, 20 Jul 2005 16:36:57 +0000</pubDate>
		<guid isPermaLink="false">/?p=191#comment-3146</guid>
		<description>One minor suggestion:  perhaps you should aviod making  the option arguments (e.g., &quot;linespoints&quot;) be strings.  If you do, then you can&#039;t do nice (eql &#039;foo) type dispatch in the methods, I believe.  I think that might make writing methods somewhat less pleasant than if the option arguments are of some type that supports EQL-testing.</description>
		<content:encoded><![CDATA[<p>One minor suggestion:  perhaps you should aviod making  the option arguments (e.g., &#8220;linespoints&#8221;) be strings.  If you do, then you can&#8217;t do nice (eql &#8216;foo) type dispatch in the methods, I believe.  I think that might make writing methods somewhat less pleasant than if the option arguments are of some type that supports EQL-testing.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anonymous</title>
		<link>http://www.nonperiodic.net/blog/2005/07/18/plotting-in-lisp-part-iii/comment-page-1/#comment-3094</link>
		<dc:creator>Anonymous</dc:creator>
		<pubDate>Wed, 20 Jul 2005 07:56:04 +0000</pubDate>
		<guid isPermaLink="false">/?p=191#comment-3094</guid>
		<description>Inheritable titles?

A series of plots which use the same x, y data lines, it would be a drag to name the title everytime, wouldn&#039;t it?

default would be to use the title as defined at the top of code
specific &quot;title:&quot; references will override the default

Other things which crop up off the top of my head....

a) ways to squish/scale multiple plots to together.
b) ways to read existing data files?
c) emacs skeleton types(equivalent) to generate simple cases of lisp code for plotting.
d) a default config file where default values can be read much like a .emacs file.</description>
		<content:encoded><![CDATA[<p>Inheritable titles?</p>
<p>A series of plots which use the same x, y data lines, it would be a drag to name the title everytime, wouldn&#8217;t it?</p>
<p>default would be to use the title as defined at the top of code<br />
specific &#8220;title:&#8221; references will override the default</p>
<p>Other things which crop up off the top of my head&#8230;.</p>
<p>a) ways to squish/scale multiple plots to together.<br />
b) ways to read existing data files?<br />
c) emacs skeleton types(equivalent) to generate simple cases of lisp code for plotting.<br />
d) a default config file where default values can be read much like a .emacs file.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
