getter-setter

Could anyone find a problem with this @property decorator? I cannot seem to get it to assert correctly. I'm sure I'm doing some really simple thing wrong, but can anyone point my tired eyes in the right direction please? class A: def __init__(self): self.a = 0 self._b = 0 @property def b(self): return self.b @b.getter def b(self): if self._b is None: return 0 return self._b @b.setter def b(self, val): self._b = (val * 20) def test_getter_setter(): obj = A() obj.a = 1 #obj.b = 2 print obj.a, obj.b obj.b = 2 print obj.a, obj.b assert obj.b == 40 test_getter_setter() The @property decorator only

When dealing with buisness classes, like the typical Customer and Employee classes, is it better to use getters and setters only or to use properties? I am translating to Delphi (for self learning) some OO examples from java books, in those examples there is always GetName() and SetName(), properties are not used. Now, I can see that if I create a component with published properties I have a very good reason for using properties, but in normal classes, which approach is better? Is the code More Readable with getters and setters (that emphasize the fact we are reading/writing a property) or

We have some Hibernate getter methods annotated with both @Column and @Basic . We get an exception if we don't have the corresponding setter. Why is this? In our case we are deriving the value returned from the getter (to get stored in the DB) and the setter has no functional purpose. So we just have an empty method to get around the error condition.. As others have mentioned, if you annotate a property getter method, then Hibernate uses the setter when reading values from the database. Basically, Hibernate assumes that anything that it is writing to the database will eventually need to be

why can I do this without any error: var testDto = ModelDto(modelId: 1) testDto.objectId = 2 while I define this: protocol DataTransferObject { var objectType: DtoType { get } var parentObjectId: Int { get set } var objectId: Int { get } var objectName: String { get set } } struct ModelDto: DataTransferObject { var objectType: DtoType var parentObjectId: Int var objectId: Int var objectName: String init(modelId: Int) { self.objectType = DtoType.Model self.objectId = modelId self.parentObjectId = -1 self.objectName = String() } } If the definition in my protocol is mostly ignored (getter,

I am having trouble understanding the concept of getters and setters in the C# language . In languages like Objective-C, they seem an integral part of the system, but not so much in C# ( as far as I can tell ). I have read books and articles already, so my question is, to those of you who understand getters & setters in C#, what example would you personally use if you were teaching the concept to a complete beginner ( this would include as few lines of code as possible )? bleepzter I think a bit of code will help illustrate what setters and getters are: public class Foo { private string bar;

Possible Duplicates: Why use getters and setters? C# 3.0 Auto-Properties - useful or not? Is there a difference between defining properties the following way - // private, with getter & setter private string fName; public string Name { get { return this.fName } set { this.fName = value } } // define as a Property public string Name { get; set;} As far as I can tell, it only looks like a stylistic preference. Am I missing something? Differences: The second form will only compile with a C# 3 compiler or later The second form doesn't let any code (even in the same class) access the field directly