Are getters and setters bad for domain object model?

[Michael_Morris]

@s_molinari

You mean the property is private to the class (encapsulated) and not readable, don’t you?

I was extending from Tom’s example. If you have a getter that will send back any property’s current value, and you don’t create a setter for one of the properties, you perforce have created a read only property.

[Michael_Morris]

@s_molinari

In the example code, they use an associative array for storing overloaded property data in the class. Is that normal practice?

No.