Not to mention, there is a school of OO thought that holds that
getters and setters are Evil with a Capital E:
no getters and setters - Google Search
http://www.javaworld.com/article/2073723/core-java/why-getter-and-setter-methods-are-evil.html
http://www.purpletech.com/blog/index.php?itemid=25
Reaching in and modifying an instance variable (or even looking at it)
violates encapsulation -- arguably the most fundamental principle of
OO. But that's a topic for a different list, so I'll shut up about it
now 
- A
···
On Fri, Mar 20, 2015 at 4:47 PM, Ryan Davis <ryand-ruby@zenspider.com> wrote:
Direct cvar/ivar access is pretty much an antipattern in my book. I still use it here and there, but I try not to.
--
Alex Chaffee - alex@stinky.com
http://alexchaffee.com
http://codelikethis.com
http://twitter.com/alexch