<?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>Tue, 18 Jun 2013 01:42:02 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Ralph Schindler's Blog: Autoloading (Revisited)]]></title>
      <guid>http://www.phpdeveloper.org/news/16880</guid>
      <link>http://www.phpdeveloper.org/news/16880</link>
      <description><![CDATA[<p>
<i>Ralph Schindler</i> has a new post to his today looking back at a sort of <a href="http://ralphschindler.com/2011/09/19/autoloading-revisited">history of autoloading</a> and some of what we've learned even in just the journey from PHP 5.0 to 5.3 (and has become best practice in the community).
</p>
<blockquote>
It wasn't until years later that certain best practices had emerged and the prolific usage of require_once/include_once throughout large bodies of code had started drying up. Even after autoloading had been adopted by larger more visible projects, a common patten had yet to emerge. [...]  Fast-forward to today, and we see that this standard for autoloading has agreed upon by a large number of projects and has come to be named the "PSR-0 autoloading standard".
</blockquote>
<p>
He covers some of the things we (the development community) have learned about autoloading and resources in our applications. He talks about the <a href="https://github.com/weierophinney/zf2/blob/master/bin/classmap_generator.php">classmap tool</a> that <i>Matthew Weier O'Phinney</i> developed (and some of its downfalls) as well as a move into PHP namespacing that has helped to make some of the "namespacing" based on class names obsolete. He's noticed a pattern in namespacing already - a self-contained structure that provides more of a "drop in" solution and how that's handled in the code.
</p>]]></description>
      <pubDate>Tue, 20 Sep 2011 09:18:55 -0500</pubDate>
    </item>
  </channel>
</rss>
