I also agree that I keep going first to the end of the file, searching the real function to launch or to reuse when reading new clojure code ...
What I would be happy with is a way to have clojure not complain before the end of a "unit of compiled code". For the REPL, that would be somewhat similar to the current behavior : wait before the end of the expression to complain for undefined symbols. For files, that would be "wait until the end of the file before complaining for undefined symbols, and let me arrange the defs in any order I feel most readable without having to think about placing those (declare) calls". Now, I don't know if this is something easily feasible in the implementation ... -- Laurent 2009/3/16 Elena <egarr...@gmail.com> > > On 16 Mar, 20:14, Jeffrey Straszheim <straszheimjeff...@gmail.com> > wrote: > > > It does effect humans reading the code, however. Often when looking at > > unfamiliar Clojure code, I find myself scrolling to the bottom first. > > That's exactly my point: why should I scroll to the bottom? That's not > the way I read a written page or report. Can you imagine a report > which starts with the details instead of the more general picture? I > think sometimes we warp ourselves to compensate for our tools > deficiencies, whilst it should be the other way around. It is much > easier for the compiler/interpreter to look ahead, isn't it? > > > > --~--~---------~--~----~------------~-------~--~----~ 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 clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en -~----------~----~----~----~------~----~------~--~---
