Basics clarification

Guest User

14y1.7kLearn iOS Programming

Hi,

Given the following code:-

private string name;

public string Name

{

get { return name; }

set { name = value; }

}

public string GetName()

{

return name;

}

public void SetName(string value)

{

name = value;

}

The first part is an example of an Automatic Get\Set property. The Get is returning the field value and the Set is setting the field value.

The second part is showing how the properties can be turned into methods to achieve the same thing.

My question is with that Constructors and Methods always seem to assign to Properties directly rather than the underlining fields as seen in the method examples GetName and SetName above? is the code just purely an example of how to achieve the same thing ie a like for like comparison?

Thanks

Steven

2 Replies

Know the answer? Post it — somebody with the same question will find it here.

Vulpes14y ago
Accepted answer
Properties are in fact translated by the C# compiler into 'get' and 'set' methods similar to what you've shown above and, in simple cases, those methods will be 'inlined' by the CLR's just in time compiler. This means (in effect) that the underlying fields will be accessed directly rather than via a method.

So, it doesn't really matter whether a constructor or method within the same class accesses a property or its underlying field directly. However, in my experience, the latter is commoner than the former.
Sam Hobbs14y ago
You say "properties can be turned into methods" but note that usually the oppoosite is done; usually it is a question of converting methods to properties. The reason for doing that is for people; to make programs more clear. If you try to understand why it is more efficient for the computer then you will fail. From the point of view of employers, people are much more expensive than computers. Software often exists to make programming easier, which supposedly saves money. Software might use more hardware resources (the computer) but save developer's time.

The advantages of properties are not obvious from simple examples. Properties are considered advantageous by experienced developers. If you were to develop an application system consisting of many programs that used fields directly (not using properties or methods such as GetName and SetName) and then later something needed to be done to the fields every timne the field is gotten or set then you will understand how much more efficient properrties would be for your time. It is developer's efficiency that is the consideration.