On Wed, Dec 10, 2008 at 2:08 PM, Stephen C. Gilardi <[EMAIL PROTECTED]> wrote: > > Alternatively, we could make those hooks be functions that one can > (optionally) define in user.clj. The platform entry point would call them if > they exist: > (ns user) > (defn init > [] > (set! *compile-path* "my/compiled/clojure")) > (defn repl-init > [] > (set! *print-length* 100) > (set! *print-level* 10) > (println "Hiya, pal!")) > > I like that because it would make for a unified story and single file to > worry about for all these initializations.
+1 to a unified story and single file :) It also has the added benefit of strongly suggesting the way other apps/frameworks should look to be initialized. For example, I can imagine an editor or IDE plugin like Enclojure calling (user/enclojure-init) on startup. - J. --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/clojure?hl=en -~----------~----~----~----~------~----~------~--~---
