News Feed
Sections




News Archive
Looking for more information on how to do PHP the right way? Check out PHP: The Right Way

Debuggable Blog:
Programming Psychology II Private methods
July 08, 2008 @ 08:44:58

According to Felix Geisendorfer's newest post on the Debuggable blog, he thinks that "private and protected methods and properties are one of the most stupid concepts of OOP."

This is a thought I first shared at CakeFest Orlando this year, but could not explain properly at the time.

He illustrates with an example of a protected "balance" variable in a BankAccount class. Sure, it's marked as private but less skilled programmers might not use it that way. He recommends a method without the getters/setters to help make the usage of the variable a bit simpler. He also suggests that using protected/private scoping helps to promote "crappy code" - using them to provide a sort of protection for code that you either don't want getting used or hiding it away so the API can't get at it.

1 comment voice your opinion now!
private method protected bad concept stupid getter setter


blog comments powered by Disqus

Similar Posts

Typical Programmer Blog: Doing it wrong: getters and setters

Matthew Weier O'Phinney's Blog: Proxies in PHP

Matthew Weir O'Phinney's Blog: PHP 5's Reflection API

Lorna Mitchell's Blog: 3 Ways to Access a Namespaced PHP Class

Web Developer Juice: PHP Magic Functions: Best Part of Object Oriented PHP - Part 2


Community Events





Don't see your event here?
Let us know!


tips developer zendserver api conference deployment interview language release framework code list introduction symfony series community laravel development podcast threedevsandamaybe

All content copyright, 2014 PHPDeveloper.org :: info@phpdeveloper.org - Powered by the Solar PHP Framework