But… what’s the the point? And… what are you saying? I don’t understand.

Are you suggesting that all properties are objects in their own right, if you squint at them the right way, so you should make them all objects? Then that would be architecture astronautics.

Or are you suggesting that an object which, in addition to the rest of its interface, has do_foo_with_bar, do_baz_with_bar, do_quux_with_bar, do_qux_with_bar, put_bar_in_frobnitz and take_bar_from_frobnitz should instead have-a Bar instance with the respective do_foo, do_baz etc methods? Then that would be plain old good OO design, and not much to make a commotion out of, assuming you don’t layer too deeply and paint yourself in a Demeter-ish corner.

Your example does nothing to help your argument. A Circumference is not an abstract concept that exists in a vacuum. It is always associated with a closed curve of some sort, and so are Radius and Area. Further, these properties are not independent of each other. If I saw your interface in real code I’d consider it horrible design.

Your example seems to suggest the architecture astronautics interpretation. That means you are either actually wasting your time thinking about abstractions of abstractions, or you picked a really awful example that doesn’t illustrate anything useful.

Makeshifts last the longest.