> > I assume that making a makro out of *define-all-properties* is not the way > to go, because it depends on the reading of a file, which should not yet > be > done at compile time (this may be a false assumption;...). > > Seems to me this is the key to how you'd construct your program. The csv file could be an artifact of your build, in which case it's got to be read at compile time and it's then when you make a top-level call to (define--all-properties) allowing you to compile (stop?), etc. If the file is input to your program, all this must be done at runtime: reading the file, calling (define-all-properties) and then loading any other code that depends on that, in effect making your program extensible.
-- -- 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/groups/opt_out.
