One small issue I see with Lisp languages over something like Haskell where side effects are greatly minimized. I tend to write code in this style:
----- (when-let [seco-files (.getMergeFilesPrimary *main-global-state*)] (merge-memory-handler-primary prim-files)) Or something similar, you don't have to understand what is going on with my logic, but if you notice 'seco-files' may return or may return something else. Also, getMergeFilesPrimary may throw an exception. If I remember, some languages like Haskell give you a little bit more power to detect what will go wrong. How do you deal with with this in Clojure? What is your coding style to prevent this. I guess I could write every function such that it returns a value, but I normally don't. And clojure code is certainly better than Java. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
