Ken Wesson <kwess...@gmail.com> writes:
>> I approached the question from the perspective of one wanting to invoke
>> Clojure-CLR with the ability to manipulate the value of
>> 'clojure.class.path' "on-the-fly" in a way that is common and natural
>> for *nix folks.
>
> And with 'env' it clearly is possible to manipulate the value on the
> fly, as Stephen pointed out three hours before your post and as you
> yourself have demonstrated.
>
> The OP's problem has been solved; let's move on.
In my opinion using a variable name that is not supported in Bash would
create some problems:
- most Linux (and probably Mac) users use the Bash shell. The 'env'
command can pass a variable that is not Bash compliant to a
process, but you can not set and query such a variable in a Bash
script. This is very likely to cause some frustration and time
wasting for people using Clojure and Bash together.
- 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
