This has come up before. You can actually work around this (search the mailing list for declare) I think that when not hacking against the REPL that the default behavior is a good one. Having to use declare bugged me a little at first, but I now consider it a very minor annoyance compared to the advantages I get from programming interactively with Clojure. Should the REPL have an "interactive" mode where it won't fire an exception on undefined symbols and instead issue compiler warnings? If compiler warnings were issued this would be a nice hook for Emacs and other IDEs. David
On Mon, Mar 16, 2009 at 3:32 PM, Elena <egarr...@gmail.com> wrote: > > 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 -~----------~----~----~----~------~----~------~--~---
