<?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, 23 May 2012 20:26:19 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Chance Garcia's Blog: Visibility and inheritance]]></title>
      <guid>http://www.phpdeveloper.org/news/13031</guid>
      <link>http://www.phpdeveloper.org/news/13031</link>
      <description><![CDATA[<p>
In <a href="http://phpprotip.com/2009/08/visibility-and-inheritance/">this recent post</a> to his blog <i>Chance Garcia</i> looks at visibility and inheritance in PHP applications. Specifically, it references a question that came up on IRC about the "default" visibility for methods and the <a href="http://en.wikipedia.org/wiki/Open/closed_principle">open/closed principle</a>.
</p>
<blockquote>
Out of the whole discussion, here is the points I got (aka understood) out of it. Please correct me in the comments if I'm off base in any way.
</blockquote>
<p>There's two points he makes in the remainder of the post:</p>
<ul>
<li>Methods should only be public when necessary.
<li>Private methods allow you to preserve the class' core functionality.
</ul>
<p>
There's also a bit of code included to illustrate some of his points.
</p>]]></description>
      <pubDate>Wed, 12 Aug 2009 09:40:20 -0500</pubDate>
    </item>
  </channel>
</rss>

