public-fields

I am aware of the advantages of using properties over fields, like being able to provide additional logic when required in the future. But I really wonder why it's not possible to use public fields for data binding or even for JSON serializers like JavaScriptSerializer class. Is there any good reason to ignore public fields in these cases? Or is it just some kind of convention? Or just to force users to use properties? The short version is that always using properties instead of public (or, really, even protected ) fields has been a fundamental design choice in .NET since the very beginning.

I know it's possible to define public instance variable with @public keyword. However, Objective-C syntax does not allow accessing other class' variable. What features should I expected from @public Ivar? Or how do I access other class' Ivars? Objective-C, as a superset of C, definitely does allow the access of public instance variables from outside the class's implementation. Now, the reason you may have heard that it isn't allowed is that it is highly discouraged. In most cases, if you want to access an instance variable outside an implementation context, you should be using accessors and

i have an inheritance struct A : public B , i want to hide individual functions from B, is this possible? i know the opposite is possible using using BMethod in the A declaration. cheers The using keyword can be used to change visibility struct A { void method1(); }; struct B: public A { void method2(); private: using A::method1; }; If you want to selectively hide functions from B it does not make much sense to use public inheritance in the first place. Use private inheritance & selectively bring methods from B into the scope of A: struct B{ void method1(){}; void method2(){}; }; struct A :

I was poking around in XNA and saw that the Vector3 class in it was using public fields instead of properties. I tried a quick benchmark and found that, for a struct the difference is quite dramatic (adding two Vectors together a 100 million times took 2.0s with properties and 1.4s with fields). For a reference type, the difference doesn't seem to be that large but it is there. So why is that? I know that a property is compiled into get_X and set_X methods, which would incur a method call overhead. However, don't these simple getters/setters always get in-lined by the JIT? I know you can't