I agree. It doesn't matter what order the compiler reads the definitions: I can scroll up and type. It does effect humans reading the code, however. Often when looking at unfamiliar Clojure code, I find myself scrolling to the bottom first.
On Mon, Mar 16, 2009 at 1:58 PM, Meikel Brandmeyer <m...@kotka.de> wrote: > Hi, > > Am 16.03.2009 um 18:36 schrieb Elena: > > IMHO, this is a no-no for interactive development. I understand that >> it helps avoiding undefined symbols, but such code integrity checks >> could be delayed to a final compilation stage. Having them earlier >> forces you to develop code in a bottom-up way. >> > > I don't think so. I start with a function. *hackhackhack* > Then I realise, that some part should be extracted into > a helper function, eg. to share code with third function. > > Then it is matter of convention of the local project, whether > this helper function is place in front or after the other functions > combined with a declare. > > I use a top-down approach all the time and it works > pretty well in Clojure. > > Sincerely > Meikel > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
