automatic-properties

I never use ivars. I only use properties -- sometimes assign properties with primitive types, and sometimes on a "private" class extension . I've seen the advantages of not using ivars in switching to ARC -- I have some borrowed code with lots of ivars that I still can't "ARC", since I don't know what needs to be retained. So I know some advantages of not using ivars, but what are the advantages of using ivars instead of properties? Note: I depend exclusively on the ivars that are automagically added in (by the compiler?) for the property declaration. Don't mark to close: I've looked at some

I just created an iOS class with the following properties: @property (nonatomic, strong) NSString* foo; @property (nonatomic, strong) NSObject* bar; @property (nonatomic) CGRect fubar; I did not put in any @synthesize or explicit ivars for these properties. I then went into the implementation file and started to create a method as follows: -(void) add I left the cursor at the end of the word "add". The following method names then popped up in code sense: addBar: (NSSet*) objects addBarObject: (objectType *) object addFoo: (NSSet*) objects addFooObject: (objectType *) object addFubar: (NSSet*)

This question already has answers here : What is the best way to give a C# auto-property an initial value? (21 answers) I came to know that C# 3.0 comes with a new feature of Auto-Implemented Properties,I liked it as we don't have to declare extra private varible in this (compare to earlier property), earlier I was using a Property i.e. private bool isPopup = true; public bool IsPopup { get { return isPopup; } set { isPopup = value; } } Now I've converted it into Auto-Implemented property i.e. public bool IsPopup { get; set; } I want to set the default value of this property to true without

If I define a struct in C# using automatic properties like this: public struct Address { public Address(string line1, string line2, string city, string state, string zip) { Line1 = line1; Line2 = line2; City = city; State = state; Zip = zip; } public string Line1 { get; protected set; } public string Line2 { get; protected set; } public string City { get; protected set; } public string State { get; protected set; } public string Zip { get; protected set; } } When I attempt to build the file, I get a compilation error saying The 'this' object cannot be used before all of its fields are assigned

Since 3.0 C# has great syntax sugar like auto-properties which a lot simplify implementation of encapsulation principle. This is good if you use it with atomic values, so you can replace encapsulation pattern like this: private string _name; public string Name { get { return _name; } set { _name = value; } } with just one line: public string FirstName { get; set; } I very like this great feature as it saves a lot of developers time. But things are not so great when you create property that points to collection. Usually I see collection properties implemented in one of two ways. 1) Without auto

I have found myself cornered, so here we go. Context I need to produce a fingerprint hash code for object diffing. Comparing the hashes of two sets of objects will need to tell me if there are identical objects with the same hash. The fingerprint hash must be platform-independent . So I went for MD5 hashing . I am working with a large Object model code base that is out of my control. All types that I will be passed for this fingerprinting can not be modified by me . I cannot add attribute or constructors or modify anything. That does not exclude that the types will change in the future. So any