<?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 21:16:37 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Michael Kimsal's Blog: Another PHP bugbear…]]></title>
      <guid>http://www.phpdeveloper.org/news/9741</guid>
      <link>http://www.phpdeveloper.org/news/9741</link>
      <description><![CDATA[<p>
<i>Micheal Kimsal</i> has <a href="http://michaelkimsal.com/blog/?p=478">pointed out</a> another "bugbear" he's found in his work with PHP - this time it's with the use of class constants.
</p>
<blockquote>
My issue is not with the language itself (this time!) but how this sort of documentation is handled. Updating public documentation well ahead of a release creates confusion.
</blockquote>
<p>
He's referring to the documentation for the class constants not quite matching up with the current functionality (resulting in a T_PAAMAYIM_NEKUDOTAYIM). He wants consistency in the documentation and maybe references to what it requires to use a certain bit of code. 
</p>]]></description>
      <pubDate>Wed, 05 Mar 2008 19:08:00 -0600</pubDate>
    </item>
  </channel>
</rss>
