Possible @property compromise

[Jacob Carlborg]

On 2013-01-30 02:40, TommiT wrote:

> I always thought that having public member variables is a bad style of
> programming because of the lack of encapsulation. So, if there's a
> language feature that enables you to write public member variables, and
> later on, replace them with property functions, wouldn't that mean that
> the language is encouraging this particular kind of bad style of
> programming?

I really don't see much point in properties/methods that just forwards 
to an instance variable.

-- 
/Jacob Carlborg