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

Symfony Blog: New in symfony 1.2: Small things matter (2)

Tim Koschuetzki's Blog: Composing Methods: Remove Assignments to Parameters

MaltBlue.com: Easy Setter Injection in Zend Framework 2

Jeff Moore's Blog: Let Your Properties be Properties

Stuart Herbert's Blog: Quick Tip: Get, Set and Query in One Method


Community Events





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


release artisanfiles tool voicesoftheelephpant composer community laravel introduction series library conference framework podcast opinion version interview list language symfony security

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