<?xml version="1.0"?>
<rss version="2.0">
  <channel>
    <title>PHPDeveloper.org</title>
    <link>http://www.phpdeveloper.org</link>
    <description>Up-to-the Minute PHP News, views and community</description>
    <language>en-us</language>
    <pubDate>Sat, 18 May 2013 07:59:55 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Derick Rethans' Blog: Circular References]]></title>
      <guid>http://www.phpdeveloper.org/news/8124</guid>
      <link>http://www.phpdeveloper.org/news/8124</link>
      <description><![CDATA[<p>
In a new post, <i>Derick Rethans</i> <a href="http://derickrethans.nl/circular_references.php">talks about</a> circular references (a reference of a memory structure back to itself) and how they relate to PHP.
</p>
<blockquote>
Circular-references has been a long outstanding issue with PHP. They are caused by the fact that PHP uses a reference counted memory allocation mechanism for its internal variables. This causes problems for longer running scripts (such as an <a href="http://blog.milkfarmsoft.com/?p=51">Application Server</a> or the <a href="http://ez.no/ezcomponents">eZ Components</a> test-suite) as the memory is not freed until the end of the request. But not everybody is aware on what exactly the problem is, so here is a small introduction to circular references in PHP.
</blockquote>
<p>
He starts by explaining what's so bad about circular references - issues not only with referencing the variable but also with freeing up the resources associated with it. He does <a href="http://derickrethans.nl/circular_references.php">suggest some solutions</a> to the issue including garbage collection and cyclic tracing.
</p>]]></description>
      <pubDate>Tue, 26 Jun 2007 09:21:00 -0500</pubDate>
    </item>
  </channel>
</rss>
