<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated on Thu, 28 Aug 2008 02:16:00 -0500 -->
<rss version="2.0">
  <channel>    <title>Codeassembly - Why are php coding guidelines important</title>
    <link>http://www.codeassembly.com/feed/comments/35</link>
    <description>CodeAssembly - Simplicity is prerequisite for reliability - Comments</description>
    <language>en-us</language>
    <managingEditor>contact@codeassembly.com</managingEditor>
    <webMaster>contact@codeassembly.com</webMaster>
    <generator>RSS Feed Generator</generator>
    <item>
      <title>Gerry</title>
      <description>function called(){
  echo 'function called<br/>';
  return 10;
}

// Under the "Optimize your code" section, you may want to fix
// that as it's still running the function every time.
// You may need to update your coding guidelines too... dunno. =P

for($i = 0; $i < $count = called(); $i++){}

/**
 * Output:
 *
 * function called
 * function called
 * function called
 * function called
 * function called
 * function called
 * function called
 * function called
 * function called
 * function called
 * function called
 */


// Perhaps the way you meant to write it:
for($i = 0, $count = called(); $i < $count; $i++){}

/**
 * Output:
 *
 * function called
 */</description>
      <link>http://codeassembly.com/Why-are-php-coding-guidelines-important/#155</link>
      <pubDate>2008-08-22 05:34:12</pubDate>
      <guid isPermaLink="true">http://codeassembly.com/Why-are-php-coding-guidelines-important/#155</guid>
    </item>
    <item>
      <title>Dadaso</title>
      <description>Really useful to develop project</description>
      <link>http://codeassembly.com/Why-are-php-coding-guidelines-important/#35</link>
      <pubDate>2007-11-15 07:22:08</pubDate>
      <guid isPermaLink="true">http://codeassembly.com/Why-are-php-coding-guidelines-important/#35</guid>
    </item>
    <item>
      <title>Harald</title>
      <description>i agree with most of your points, even though i don't like your coding-guidelines. but that's a very subjectiv point of view ;-). however:

in projects where you will not only have php code but javascript, perl, shell, whatever else phpdoc might not be the best solution, because i think the source-code documentation should look the same across all languages. i've tried several solutions for this and are now using robodoc, which i like very much. it won't analyse your source-code and therefore most time it's a lot more to write to document your code. on the other hand you have unified documentation for all your source-files - and i mean really all: you can even write documentation for your configuration-files for example.
</description>
      <link>http://codeassembly.com/Why-are-php-coding-guidelines-important/#26</link>
      <pubDate>2007-11-06 13:57:06</pubDate>
      <guid isPermaLink="true">http://codeassembly.com/Why-are-php-coding-guidelines-important/#26</guid>
    </item>
  </channel></rss>