<?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>Fri, 24 May 2013 06:18:47 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Stefan Koopmanschap's Blog: public static vs static public ]]></title>
      <guid>http://www.phpdeveloper.org/news/11825</guid>
      <link>http://www.phpdeveloper.org/news/11825</link>
      <description><![CDATA[<p>
<i>Stefan Koopmanschap</i> has <a href="http://www.leftontheweb.com/message/public_static_vs_static_public">posted about static methods</a> and comparing "static public" to "public static" (including a popularity graph).
</p>
<blockquote>
Ever since starting with PHP 5 object oriented development, all documentation I read on the topic seemed to suggest that the only way to write the method keywords is "public static". I've been following along those lines, and for a while I really thought any other order would trigger errors. Only recently I found out the other way round is actually nicer.
</blockquote>
<p>
In his opinion, the "static public" keyword combination (versus "public static") is "more beautiful" than its inverse counterpart. He even asked about it in a twitpoll and got <a href="http://www.leftontheweb.com/images/twtpoll_staticpublic.png">these results</a> - "public static" winning out as the popular choice. If you want to voice your opinion, you can still <a href="http://twtpoll.com/r/al5xq4">get in on the poll</a>.
</p>]]></description>
      <pubDate>Tue, 27 Jan 2009 12:07:10 -0600</pubDate>
    </item>
  </channel>
</rss>
