<?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>Don’t Wait! Order The CHEAPEST MEDICATIONS NOW &raquo; Vastarel Online Without Prescription</title>
	<atom:link href="http://goesping.org/archives/2005/11/26/thanksgiving-computer-languages/feed/" rel="self" type="application/rss+xml" />
	<link>http://goesping.org/archives/2005/11/26/thanksgiving-computer-languages/</link>
	<description>Pinging stuff I care about.</description>
	<lastBuildDate>Wed, 05 Jan 2011 09:01:21 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>Don’t Wait! Order The CHEAPEST MEDICATIONS NOW &raquo; Vastarel Online Without Prescription</title>
		<link>http://goesping.org/archives/2005/11/26/thanksgiving-computer-languages/comment-page-1/#comment-17640</link>
		<dc:creator>Ed That Goes Ping</dc:creator>
		<pubDate>Sun, 15 Jun 2008 15:32:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.goesping.org/?p=724#comment-17640</guid>
		<description>It makes sense in retrospect I guess -- and it *would* be nice not to have to use &quot;lst&quot; as the name of a variable for a generic list in a generic list-processing function.   Thanks! :)</description>
		<content:encoded><![CDATA[<p>It makes sense in retrospect I guess &#8212; and it *would* be nice not to have to use &#8220;lst&#8221; as the name of a variable for a generic list in a generic list-processing function.   Thanks! :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>Don’t Wait! Order The CHEAPEST MEDICATIONS NOW &raquo; Vastarel Online Without Prescription</title>
		<link>http://goesping.org/archives/2005/11/26/thanksgiving-computer-languages/comment-page-1/#comment-17638</link>
		<dc:creator>Daniel Weinreb</dc:creator>
		<pubDate>Sun, 15 Jun 2008 15:16:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.goesping.org/?p=724#comment-17638</guid>
		<description>The business of using #&#039; is because Common Lisp is what&#039;s called a &quot;Lisp-2&quot;, a Lisp with separate value cells and function cells.  Scheme is a &quot;Lisp-1&quot;.  For the best discussion of this topic, see

http://www.nhplace.com/kent/Papers/Technical-Issues.html

Kent Pitman and Richard Gabriel explain it all.

Here&#039;s one simple thing:  There&#039;s a function called &quot;list&quot;, but it&#039;s useful to be able to use &quot;list&quot; as a variable name.

Common Lisp had to be a Lisp-2 in order to compatibly run the vast majority of existing Lisp code that existed in the ancestor dialects.  We didn&#039;t have any real choice in the matter.  It was highly controversial, nevertheless, during the original Common Lisp design.</description>
		<content:encoded><![CDATA[<p>The business of using #&#8217; is because Common Lisp is what&#8217;s called a &#8220;Lisp-2&#8243;, a Lisp with separate value cells and function cells.  Scheme is a &#8220;Lisp-1&#8243;.  For the best discussion of this topic, see</p>
<p><a href="http://www.nhplace.com/kent/Papers/Technical-Issues.html" rel="nofollow">http://www.nhplace.com/kent/Papers/Technical-Issues.html</a></p>
<p>Kent Pitman and Richard Gabriel explain it all.</p>
<p>Here&#8217;s one simple thing:  There&#8217;s a function called &#8220;list&#8221;, but it&#8217;s useful to be able to use &#8220;list&#8221; as a variable name.</p>
<p>Common Lisp had to be a Lisp-2 in order to compatibly run the vast majority of existing Lisp code that existed in the ancestor dialects.  We didn&#8217;t have any real choice in the matter.  It was highly controversial, nevertheless, during the original Common Lisp design.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Don’t Wait! Order The CHEAPEST MEDICATIONS NOW &raquo; Vastarel Online Without Prescription</title>
		<link>http://goesping.org/archives/2005/11/26/thanksgiving-computer-languages/comment-page-1/#comment-5867</link>
		<dc:creator>Ed That Goes Ping</dc:creator>
		<pubDate>Mon, 28 Nov 2005 05:36:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.goesping.org/?p=724#comment-5867</guid>
		<description>Cool.  The Rails book is still calling my name.

As is Why&#039;s Poignant Guide to Ruby.</description>
		<content:encoded><![CDATA[<p>Cool.  The Rails book is still calling my name.</p>
<p>As is Why&#8217;s Poignant Guide to Ruby.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Don’t Wait! Order The CHEAPEST MEDICATIONS NOW &raquo; Vastarel Online Without Prescription</title>
		<link>http://goesping.org/archives/2005/11/26/thanksgiving-computer-languages/comment-page-1/#comment-5866</link>
		<dc:creator>James</dc:creator>
		<pubDate>Sun, 27 Nov 2005 05:29:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.goesping.org/?p=724#comment-5866</guid>
		<description>I&#039;ve spent a good chunk of the past few days immersed in the Ruby on Rails book. I&#039;m very impressed, though I&#039;m also a Ruby newbie. The test will be when I get back to my test apps with the new knowledge I&#039;ve acquired, but every time I&#039;ve found myself thinking &quot;yes, but I need to be able to do X&quot; the next section has covered it.

The hype is going to hurt Rails, particularly with way too many people touting it as a replacement for Java. But for medium sized web apps, it seems like a great option.</description>
		<content:encoded><![CDATA[<p>I&#8217;ve spent a good chunk of the past few days immersed in the Ruby on Rails book. I&#8217;m very impressed, though I&#8217;m also a Ruby newbie. The test will be when I get back to my test apps with the new knowledge I&#8217;ve acquired, but every time I&#8217;ve found myself thinking &#8220;yes, but I need to be able to do X&#8221; the next section has covered it.</p>
<p>The hype is going to hurt Rails, particularly with way too many people touting it as a replacement for Java. But for medium sized web apps, it seems like a great option.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

