<?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 23:22:04 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Tim's Blog: Rethinking extract() By Convention]]></title>
      <guid>http://www.phpdeveloper.org/news/4704</guid>
      <link>http://www.phpdeveloper.org/news/4704</link>
      <description><![CDATA[In <a href="http://www.designbytim.com/2006/01/20/rethinking-extract-by-convention/">this latest post</a> from his blog, <i>Tim</i> looks back at his <a href="http://www.phpdeveloper.org/news/4691">previous post</a> ("Learn to extract()") and summarizes some of the feedback he got.
<p>
<quote>
<i>
Since posting <a href="http://www.designbytim.com/2006/01/18/learn-to-extract">Learn To extract();</a> I have gotten a lot of great criticism that has helped me revise my thinking of the uses for extract(). Along with reading <a href="http://www.sitepoint.com/blogs/2005/08/15/the-problem-with-extract/">The Problem With 'extract'</a> on SitePoint - here is my conclusion to when/where to use extract.
</i>
</quote>
<p>
He <a href="http://www.designbytim.com/2006/01/20/rethinking-extract-by-convention/">changes his stance</a> on its use after learning more from comments made and the <a href="http://www.sitepoint.com/blogs/2005/08/15/the-problem-with-extract/">SitePoint blog post</a> talking about the issues it can cause...]]></description>
      <pubDate>Mon, 23 Jan 2006 06:51:12 -0600</pubDate>
    </item>
  </channel>
</rss>
