I very much agree, but saying it in such a way won't help others to understand that. That is persons that haven't understood the significant difference right now.
I would be interested in why it is considered a terrible practice. That it's slow might be a good point but for performance critical stuff I use D and for larger web project Ruby on Rails (where performance is a whole…
The example is the most simple way I could think of. It should only show that is is possible not what is the perfect solution (if there is any). Of course you could throw in some runtime reflection and variable function…
I agree that getters and setters aren't object oriented. It was the whole point of my blog post to make people think about that. It wasn't written for people who already understand that, though… otherwise it would be…
I very much agree, but saying it in such a way won't help others to understand that. That is persons that haven't understood the significant difference right now.
I would be interested in why it is considered a terrible practice. That it's slow might be a good point but for performance critical stuff I use D and for larger web project Ruby on Rails (where performance is a whole…
The example is the most simple way I could think of. It should only show that is is possible not what is the perfect solution (if there is any). Of course you could throw in some runtime reflection and variable function…
I agree that getters and setters aren't object oriented. It was the whole point of my blog post to make people think about that. It wasn't written for people who already understand that, though… otherwise it would be…