Several comments: (a) 'clojure.load.path' is not new in 1.3. It's been in the code since at least May, 2009. (b) Regarding Dimitre's comment below, I probably did have Java system properties on my mind at the time. I guarantee that I was not thinking of picking Bash-compliant names. I doubt that I gave it much thought at all. (c) It could be changed to something like CLOJURE_LOAD_PATH instead. Would that cause a problem for anyone?
-David On Aug 17, 3:25 pm, Dimitre Liotev <lio...@gmail.com> wrote: > - A name like clojure.load.path breaks a widely accepted convention: > environment variable names usually consist of capital letters and > underscores. So we have MAVEN_HOME, JAVA_HOME, ANT_HOME, etc. When > I see a name like clojure.load.path my first thought would be that > this is a Java system property, not an environment variable. > > I think that it would be wise to stick to the convention and use > variable names that are Bash compliant. I would use CLOJURE_LOAD_PATH > for an environment variable name and clojure.load.path for a Java system > property name. > > -- > Dimitre Liotev -- 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
