> 3) On a super minor nit-picky note, I was surprised that some of the > '(pr ...)' ish methods didn't return the result of what they were > printing. One of the very first things I wanted to do was to wrap > another expression around (pr ..) for debugging purposes, but since it > didn't return its argument, I couldn't do this (it broke the higher up > expression using the value). Granted writing my own version that did > just this was super trivial, but I find myself wondering why you > wouldn't want functions to always return something if at all possible, > for convenience just in case it needs to be used. Maybe I'm missing a > conceptual reason why this is so?
Sorry, I'm noobish enough that I can only answer the third point. (pr) is used to print a representation that the compiler will understand later, (print) is for humans to read. Sort of like the difference between __str__ and __repr__ in python, if you've used that. Look at (println-str) that might do what you're looking for. HTH, Allen --~--~---------~--~----~------------~-------~--~----~ 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 To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/clojure?hl=en -~----------~----~----~----~------~----~------~--~---
