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 with properties (that at first sight can be confused with parameterless methods)?
No. Getters and setters are only there in Java because it doesn’t have properties. It makes for much cleaner code to use properties. And then if you need a getter or a setter, you can build it into the property, but you don’t have to litter the accessing code with a bunch of function calls.