<?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/"
	xmlns:creativeCommons="http://backend.userland.com/creativeCommonsRssModule"	>
<channel>
	<title>Comments on: Logging and Debugging in Clojure, or How Macros and Functional Programming Saved the Day (again) [part 1]</title>
	<atom:link href="http://wave.thewe.net/2009/11/22/logging-and-debugging-in-clojure/feed/" rel="self" type="application/rss+xml" />
	<link>http://wave.thewe.net/2009/11/22/logging-and-debugging-in-clojure/</link>
	<description>Developing powerful foundations for adaptable information-centric applications with Google Wave</description>
	<lastBuildDate>Fri, 12 Feb 2010 21:19:17 -0800</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Logging and Debugging in Clojure &#8211; Followup (Complete Tracing)</title>
		<link>http://wave.thewe.net/2009/11/22/logging-and-debugging-in-clojure/comment-page-1/#comment-742</link>
		<dc:creator>Logging and Debugging in Clojure &#8211; Followup (Complete Tracing)</dc:creator>
		<pubDate>Thu, 17 Dec 2009 12:40:05 +0000</pubDate>
		<guid isPermaLink="false">http://blog.thewe.net/?p=140#comment-742</guid>
		<description>[...] some interesting comments on our previous blog post we thought it would be appropriate to emphasize the added value of our logging approach (which [...]</description>
		<content:encoded><![CDATA[<p>[...] some interesting comments on our previous blog post we thought it would be appropriate to emphasize the added value of our logging approach (which [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Luis Sergio Oliveira</title>
		<link>http://wave.thewe.net/2009/11/22/logging-and-debugging-in-clojure/comment-page-1/#comment-628</link>
		<dc:creator>Luis Sergio Oliveira</dc:creator>
		<pubDate>Thu, 03 Dec 2009 06:53:49 +0000</pubDate>
		<guid isPermaLink="false">http://blog.thewe.net/?p=140#comment-628</guid>
		<description>Hi Ayal,

isn&#039;t that a bit similar to Common Lisp trace facility (http://www.lispworks.com/documentation/HyperSpec/Body/m_tracec.htm)? Doesn&#039;t Clojure sports its own (it seams to http://clojure.org/libraries#toc29)?

I understand that logging for admin purposes may require something different from trace, something that may be persisted and probably that is your goal, but, in principle you could do that on top of trace, couldn&#039;t you?</description>
		<content:encoded><![CDATA[<p>Hi Ayal,</p>
<p>isn&#8217;t that a bit similar to Common Lisp trace facility (<a href="http://www.lispworks.com/documentation/HyperSpec/Body/m_tracec.htm)?" rel="nofollow">http://www.lispworks.com/documentation/HyperSpec/Body/m_tracec.htm)?</a> Doesn&#8217;t Clojure sports its own (it seams to <a href="http://clojure.org/libraries#toc29)?" rel="nofollow">http://clojure.org/libraries#toc29)?</a></p>
<p>I understand that logging for admin purposes may require something different from trace, something that may be persisted and probably that is your goal, but, in principle you could do that on top of trace, couldn&#8217;t you?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Scott</title>
		<link>http://wave.thewe.net/2009/11/22/logging-and-debugging-in-clojure/comment-page-1/#comment-627</link>
		<dc:creator>Scott</dc:creator>
		<pubDate>Thu, 03 Dec 2009 05:39:20 +0000</pubDate>
		<guid isPermaLink="false">http://blog.thewe.net/?p=140#comment-627</guid>
		<description>This is awesome. Seriously, thank you! Coming from amazing Smalltalk debuggers not having a good debugger is my biggest annoyance with Clojure.

I thought about writing an emacs function that would look at the function at point and you could select which variables you wanted printed and it would add print statements before them in the code, and then with an arg this function would remove all print statements from the current function.

Anyway, awesome contribution!</description>
		<content:encoded><![CDATA[<p>This is awesome. Seriously, thank you! Coming from amazing Smalltalk debuggers not having a good debugger is my biggest annoyance with Clojure.</p>
<p>I thought about writing an emacs function that would look at the function at point and you could select which variables you wanted printed and it would add print statements before them in the code, and then with an arg this function would remove all print statements from the current function.</p>
<p>Anyway, awesome contribution!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Julian Morrison</title>
		<link>http://wave.thewe.net/2009/11/22/logging-and-debugging-in-clojure/comment-page-1/#comment-622</link>
		<dc:creator>Julian Morrison</dc:creator>
		<pubDate>Wed, 02 Dec 2009 16:51:07 +0000</pubDate>
		<guid isPermaLink="false">http://blog.thewe.net/?p=140#comment-622</guid>
		<description>You might not need to walk the code, if you can rebind the vars (the &quot;function names&quot;) to logged versions of themselves at the top level.</description>
		<content:encoded><![CDATA[<p>You might not need to walk the code, if you can rebind the vars (the &#8220;function names&#8221;) to logged versions of themselves at the top level.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Raoul Duke</title>
		<link>http://wave.thewe.net/2009/11/22/logging-and-debugging-in-clojure/comment-page-1/#comment-604</link>
		<dc:creator>Raoul Duke</dc:creator>
		<pubDate>Tue, 01 Dec 2009 01:58:58 +0000</pubDate>
		<guid isPermaLink="false">http://blog.thewe.net/?p=140#comment-604</guid>
		<description>yeah, as a long time code maintainer, i&#039;ve always thought that should be doable and useful. thanks for telling me i&#039;m not insane, or at least that i&#039;m not the only one.</description>
		<content:encoded><![CDATA[<p>yeah, as a long time code maintainer, i&#8217;ve always thought that should be doable and useful. thanks for telling me i&#8217;m not insane, or at least that i&#8217;m not the only one.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tweets that mention Logging and Debugging in Clojure, or How Macros and Functional Programming Saved the Day (again) -- Topsy.com</title>
		<link>http://wave.thewe.net/2009/11/22/logging-and-debugging-in-clojure/comment-page-1/#comment-546</link>
		<dc:creator>Tweets that mention Logging and Debugging in Clojure, or How Macros and Functional Programming Saved the Day (again) -- Topsy.com</dc:creator>
		<pubDate>Sun, 22 Nov 2009 11:32:12 +0000</pubDate>
		<guid isPermaLink="false">http://blog.thewe.net/?p=140#comment-546</guid>
		<description>[...] This post was mentioned on Twitter by theWE.net, theWE.net. theWE.net said: logging and debugging in clojure: http://blog.thewe.net/2009/11/22/logging-and-debugging-in-clojure/ [...]</description>
		<content:encoded><![CDATA[<p>[...] This post was mentioned on Twitter by theWE.net, theWE.net. theWE.net said: logging and debugging in clojure: <a href="http://blog.thewe.net/2009/11/22/logging-and-debugging-in-clojure/" rel="nofollow">http://blog.thewe.net/2009/11/22/logging-and-debugging-in-clojure/</a> [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
