3 ms·

It's bad, in the sense that it leads you to write tightly coupled code that depends on it. The whole point of objects are to hide data and instead expose behav

It's bad, in the sense that it leads you to write tightly coupled code that depends on it. The whole point of objects are to hide data and instead expose behavior so other code is coupled to the objects behavior rather than its internal implementation on a specific set of chosen data. This leaves you free to fiddle with the internal implementation without breaking the external API, which leads to modular loosely coupled code.

protomyth 15y ago
It also allows the substitution of internal data structures due to profiling / runtime usage of the data.
- gnaritas 15y ago
  Which is the point of modular code, to be able to fiddle with the internals for whatever reason you like without affecting clients.
  - protomyth 15y ago
    agreed, I was pointing out (badly) that it could be a runtime / compiler decision and not the programmer.
shasta 15y ago
But note that this is an argument for encapsulating data and not necessarily bundling it with methods as objects. You can hide data reps with functions.