<?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: Finding Circular Reference leaks in Perl</title>
	<atom:link href="http://letsgetdugg.com/2009/04/19/finding-circular-reference-leaks-in-perl/feed/" rel="self" type="application/rss+xml" />
	<link>http://letsgetdugg.com/2009/04/19/finding-circular-reference-leaks-in-perl/</link>
	<description>Random tech jargon</description>
	<lastBuildDate>Mon, 06 Sep 2010 09:29:35 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: victori</title>
		<link>http://letsgetdugg.com/2009/04/19/finding-circular-reference-leaks-in-perl/comment-page-1/#comment-166</link>
		<dc:creator>victori</dc:creator>
		<pubDate>Wed, 30 Dec 2009 21:22:58 +0000</pubDate>
		<guid isPermaLink="false">http://letsgetdugg.com/?p=43#comment-166</guid>
		<description>I would have to agree with j_king, reference counting garbage collection is extremely predictable compared to say the JVM GC algorithms. Sure some patterns such as the &lt;a href=&quot;http://en.wikipedia.org/wiki/Strategy_pattern&quot; rel=&quot;nofollow&quot;&gt;strategy pattern&lt;/a&gt; might be more difficult to implement correctly without leaking, but at the end of the day garbage collection times are predictable.

** by strategy pattern I mean a strategy implementation that will need access to the parent instance creating a circular reference leak.</description>
		<content:encoded><![CDATA[<p>I would have to agree with j_king, reference counting garbage collection is extremely predictable compared to say the JVM GC algorithms. Sure some patterns such as the <a href="http://en.wikipedia.org/wiki/Strategy_pattern" rel="nofollow">strategy pattern</a> might be more difficult to implement correctly without leaking, but at the end of the day garbage collection times are predictable.</p>
<p>** by strategy pattern I mean a strategy implementation that will need access to the parent instance creating a circular reference leak.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: j_king</title>
		<link>http://letsgetdugg.com/2009/04/19/finding-circular-reference-leaks-in-perl/comment-page-1/#comment-164</link>
		<dc:creator>j_king</dc:creator>
		<pubDate>Wed, 23 Dec 2009 20:13:21 +0000</pubDate>
		<guid isPermaLink="false">http://letsgetdugg.com/?p=43#comment-164</guid>
		<description>@Ted

Why is it unbelievable? Python uses it too. I imagine quite a few other interpreted languages do as well. They all have practical reasons for it.

Most notably, low overhead and ease of implementation.</description>
		<content:encoded><![CDATA[<p>@Ted</p>
<p>Why is it unbelievable? Python uses it too. I imagine quite a few other interpreted languages do as well. They all have practical reasons for it.</p>
<p>Most notably, low overhead and ease of implementation.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ted Henry</title>
		<link>http://letsgetdugg.com/2009/04/19/finding-circular-reference-leaks-in-perl/comment-page-1/#comment-160</link>
		<dc:creator>Ted Henry</dc:creator>
		<pubDate>Thu, 17 Dec 2009 05:56:46 +0000</pubDate>
		<guid isPermaLink="false">http://letsgetdugg.com/?p=43#comment-160</guid>
		<description>Thanks for the article.

It is unbelievable in this day and age that a memory-managed language would use reference counting. Bad, Perl. Bad.</description>
		<content:encoded><![CDATA[<p>Thanks for the article.</p>
<p>It is unbelievable in this day and age that a memory-managed language would use reference counting. Bad, Perl. Bad.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andy Lester</title>
		<link>http://letsgetdugg.com/2009/04/19/finding-circular-reference-leaks-in-perl/comment-page-1/#comment-34</link>
		<dc:creator>Andy Lester</dc:creator>
		<pubDate>Wed, 06 May 2009 19:09:22 +0000</pubDate>
		<guid isPermaLink="false">http://letsgetdugg.com/?p=43#comment-34</guid>
		<description>Note that you can do automated testing of these leaks with Test::Memory::Cycle, which wraps around Devel::Cycle.</description>
		<content:encoded><![CDATA[<p>Note that you can do automated testing of these leaks with Test::Memory::Cycle, which wraps around Devel::Cycle.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
