On Jul 20, 2010, at 2:27 PM, Chas Emerick wrote: > Top-level calls are definitely frowned upon (and almost never necessary). > Almost by definition, they're side-effecting, and you're not always in > control of when code is loaded (e.g. if someone is using your code as a > library, top-level calls are decidedly irritating). >
Okay. FWIW in my case I'm generally not providing a library and I generally AM in control of when code is loaded, as long as my IDE isn't doing it behind my back :-). I guess in most cases I can get used to putting all of my top-level stuff in a concisely-named function that I later call, although my main working mode is to have a bunch of top-level calls in a short file that I re-load after reloading definitions in my other files... And it'd be a little bit of a pain to have to type calls rather than just hitting the reload key sequence... not a huge pain, but I'll probably try to keep doing this as long as my tools let me. In any event, I find it hard to imagine any circumstance in which I'll want reloading to happen independent of my request. -Lee -- Lee Spector, Professor of Computer Science School of Cognitive Science, Hampshire College 893 West Street, Amherst, MA 01002-3359 lspec...@hampshire.edu, http://hampshire.edu/lspector/ Phone: 413-559-5352, Fax: 413-559-5438 Check out Genetic Programming and Evolvable Machines: http://www.springer.com/10710 - http://gpemjournal.blogspot.com/ -- 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
