[TYPES] The type/object distinction and possible synthesis of OOP and imperative programming languages

[Chris Angelico]

On Sat, Apr 20, 2013 at 1:31 AM, Roy Smith <roy at panix.com> wrote:
> #define private public
> #define protected public
> #include <whatever.h>

And:
#define class struct

But what I mean is that, _in my design_, I make everything public. No
getters/setters, just direct member access. The theory behind getters
and setters is that you can change the implementation without changing
the interface... but I cannot remember a *single time* when I have
made use of that flexibility. Not one. Nor a time when I've wished for
that flexibility, after coding without it. No no, not one!

ChrisA
(He's telling the truth, he is not Mabel.)