> Coming from an OO background which puts a strong focus on data > encapsulation, > this makes me a little nervous.
The same problem exists with OO. For example, maybe you return a Headers object from a request. A couple of releases down the line you realize you need to include some additional info, and now your request method returns a Response, which has a getHeaders method. Clients break. Any use of library code that actually looks at the return value is prone to this. API changes require code changes. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
