in reply to Re^7: (OT) OOUI: multiple views in an object.
in thread (OT) OOUI: multiple views in an object.

but I don't see why I need to do it when I don't see any particular problems with my current model.

Agreed. And in the present case, a purely procedural solution from the outset would be perfectly fine in my mind. It isn't a complex system.

Incidently, I read over the author's article Why getter and setter methods are evil. It appears he doesn't think all get and set methods are evil--just the ones that are expected to return a primitive type. Returning more complex objects is fine by him.

Well yes, I don't even consider methods that deal in non-primitive objects (eg, domain level or interface level objects) to be getter/setter methods.

  • Comment on Re^8: (OT) OOUI: multiple views in an object.