OK. Thanks.
Regarding "why so many atoms": I have rewritten a GUI-based (Swing) app to Clojure (our company's product: A Java applet), and where I previously typically had extended JPanels, adding variables and methods to them, I have (for now) replaced them with maps in atoms, where the maps contain the same data (including the actual panel, which I prevously extended), and even som "methods" to work on those values, and then I am able to pass around "references" to data which can be altered with swap! - basically a form of mutable state. Not ideal, and I am certainly intend to refactor the code to make it more functional, but I am not sure how to better implement a more complex event-driven GUI application. I have your book, but haven't read most of it yet. Am still reading Clojure in Action. Any part of your book I should skip to directly that is specific to my problem? Any good articles og code samples you can point me to? On 26 Aug, 16:42, Fogus <mefo...@gmail.com> wrote: > I guess the first question is; why so many atoms? But regardless, > there is no standard for naming such things. If you know you're > dealing with atoms only (as opposed to a reference in general) then > something like `foo-atom` would suffice I'd say. -- 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