On Sun, Jun 17, 2012 at 1:32 PM, Kurt Harriger <kurtharri...@gmail.com> wrote: > If you follow the > hollywood principle you don't need getters... but you do need side-effects.
This might be where you're getting stuck then? Perhaps "the hollywood principle" isn't the best approach? If you think it really requires side-effects, you're going to have to abandon it in order to use Clojure effectively... > in clojure getters are the only abstraction to protect > my code from changes to data representations. Not true. The data-as-API exposed to client code does not have to match the internal data representation. For example, consider operations that use transients internally - their API is still based on persistent (immutable) data structures but their data representation is based on (mutable) transient data structures. Similarly, Clojure APIs can and are built around Java libraries, that offer a persistent (immutable) data structure to Clojure client code, whilst maintaining some nasty mutable Java data representation internally. Hope that helps? If not, watching some of those videos really will help... -- Sean A Corfield -- (904) 302-SEAN An Architect's View -- http://corfield.org/ World Singles, LLC. -- http://worldsingles.com/ "Perfection is the enemy of the good." -- Gustave Flaubert, French realist novelist (1821-1880) -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en
