On Saturday, December 5, 2015 at 8:04:34 PM UTC-6, tbc++ wrote: > > Also, if you have so many atoms in your program that it becomes hard to > remember where they are, that would be another source of concern ;-) >
Yeah .... I'm worried that I'll come back to the code a year later and not remember that the variable contains an atom, and wonder why I'm getting different things out of it. Though I suppose the at-sign might be a tip-off. Or suppose I have a recurrent role in several functions or several namespaces or several programs, for which I always use the same name. Using the same name in different contexts makes the meaning of the variables clear. Then it turns out that I have to make a new special version of this kind of program, in which I need to store the same kind of data in an atom rather than simply passing it from function to function. I want to give the variable containing the data the same name ... but I don't, because this variable is different--it contains an atom containing the usual data, rather than the data itself. (This is actually the situation that prompted the question. I don't like having to store the data in an atom, but ) -- 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 --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
