<?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>Sun, 07 Sep 2008 03:05:11 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Matthew Turland's Blog: The Yin and Yang of Typing]]></title>
      <guid>http://www.phpdeveloper.org/news/9546</guid>
      <link>http://www.phpdeveloper.org/news/9546</link>
      <description><![CDATA[<p>
A little while back <i>Matthew Turland</i> <a href="http://ishouldbecoding.com/2008/01/19/the-yin-and-yang-of-typing/">posted about</a> something that some developers moving over to PHP from more strict languages have an issue with - variable typing - and how its evolved in languages over time.
</p>
<blockquote>
Without a little background in programming languages or computer science in general, it's entirely possible that <a href="http://en.wikipedia.org/wiki/Type_system">typing systems</a> are not something that have crossed your mind. I thought I'd take a blog entry to share some of my thoughts on how it's affecting the creation and evolution of languages.
</blockquote>
<p>
He walks through history a bit, mentioning C, Java, Python and PHP and how they differ in their default type handling. He especially focuses on the "blurred line" between strong and weak typing and how some if offers special features to the language that uses the method.
</p>]]></description>
      <pubDate>Fri, 01 Feb 2008 11:58:00 -0600</pubDate>
    </item>
    <item>
      <title><![CDATA[Nick Halstead's Blog: Do faster typists make better coders?]]></title>
      <guid>http://www.phpdeveloper.org/news/8331</guid>
      <link>http://www.phpdeveloper.org/news/8331</link>
      <description><![CDATA[<p>
<i>Nick Halstead</i> <a href="http://blog.assembleron.com/2007/07/24/do-faster-typists-make-better-coders/">asks an interesting question</a> on his blog today - "Do faster typists make better coders?"
</p>
<blockquote>
<p>
I have been able to touch type since about age 12 and can manage about 100 words per minute when faced with blocks of text to copy and even faster if I am just writing code. [...] Programming in C meant a lot more typing of parenthesis and a lot more thinking about the structure of the code.
</p>
<p>
PHP has introduced another set of typing problems with a lot more use of < > and a much higher mixture of variables/functions/parenthesis plus the added bonus of trying to remember a single function from a choice of 3000+.
</p>
</blockquote>
<p>
Several of <a href="http://blog.assembleron.com/2007/07/24/do-faster-typists-make-better-coders/#comments">the comments on the post</a> suggest that it could be helpful to productivity, but shouldn't be focused on too much. After all, what really matters is the programmers skill, right?
</p>]]></description>
      <pubDate>Wed, 25 Jul 2007 14:51:04 -0500</pubDate>
    </item>
    <item>
      <title><![CDATA[Brian Moon's Blog: Initializing & typing variables with settype()]]></title>
      <guid>http://www.phpdeveloper.org/news/6269</guid>
      <link>http://www.phpdeveloper.org/news/6269</link>
      <description><![CDATA[<p>
In <a href="http://doughboy.wordpress.com/2006/09/14/initializing-typing-variables-with-settype/">his latest post</a>, <i>Brian Moon</i> talks about a method to help you and your code fit into an E_STRICT style of coding - the <a href="http://www.php.net/settype">settype function</a>.
</p>
<blockquote>
These days, the way to develop is to have E_ALL and maybe even throw in E_STRICT if you are really hard core. That of course means having all your variables initialized before they are used.
</blockquote>
<p>
In <a href="http://doughboy.wordpress.com/2006/09/14/initializing-typing-variables-with-settype/">his view</a>, defining them is good, but it's more "elegant" to use the settype function to make it more clear where they are defined. He also includes a function, using settype, that ensures that the entered values are what they should be (i.e. and int is an int).
</p>]]></description>
      <pubDate>Thu, 14 Sep 2006 07:01:47 -0500</pubDate>
    </item>
  </channel>
</rss>
