<?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>Wed, 19 Jun 2013 15:39:48 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Paul Jones' Blog: Line Length, Volume, and Density]]></title>
      <guid>http://www.phpdeveloper.org/news/9775</guid>
      <link>http://www.phpdeveloper.org/news/9775</link>
      <description><![CDATA[<p>
In a <a href="http://paul-m-jones.com/?p=276">new blog post</a>, <i>Paul Jones</i> looks at three aspects of coding style - line length, volume and density - and how different people have different assumptions as to what's "right".
</p>
<blockquote>
When it comes to coding style, there are are various ideas about how you should write the individual lines of code. The usual argument is about "how long should a line of code be"? There's more to it than that, though. Developers should also take into account line volume ("number of lines") and line density ("instructions per line").
</blockquote>
<p>
He mentions the <A href="http://pear.php.net/manual/en/standards.php">PEAR style guide</a> when talking about line length, reading code like and sentence in line volume/density and how the "shorter is better" concept can be pushed to its extreme limits taking code into the unreadable zone.
</p>]]></description>
      <pubDate>Tue, 11 Mar 2008 09:33:00 -0500</pubDate>
    </item>
  </channel>
</rss>
