3 ms·
Getters and setters are much more useful when accessing or setting the element should require some other function calls. Caching, memoization, and event-logging
by karpierz 4y ago
Getters and setters are much more useful when accessing or setting the element should require some other function calls. Caching, memoization, and event-logging are examples where you might want this to happen.
You can say that's not a getter/setter, but then your definition is just different than the people you're responding to.
- ratww 4y agoHowever Getters/Setters are often the worst place to implement cross-cutting concerns, like caching, memoization and logging. Of course, in more limited languages/environments they're probably the only tool you have, so there's that.
- Xeoncross 4y agoCaching, memoization, and event-logging can be handled by wrapper objects that implement the interface so the base object doesn't need to contain all these layers of outside concerns. Let each class focus on it's single area of use. interface Store { Query() } // these all have the Query() method type/class MySQL implements Store type/class Cache implements Store type/class Logger implements Store var db Store db = new Logger(new Cache(new MySQL()))