> are not necessarily idiots,
Ooof.. bad choice of words there on my part, it was in jest and I did not mean
literal "idiots". :-p
On Jun 30, 2010, at 5:48 PM, Greg wrote:
>> However, I don't see it helping newcomers to Clojure significantly
>
> With respect, I'm a newcomer to Clojure, and the
> Sounds sensible in principle, though I think the issue for n00bs is
> that configuring *anything* is a barrier because even the slightest
> mistake in interpreting the documentation or configuring your
> environment is pretty painful.
OK, see my response to Rick. I think we're getting stuck on a
We use a "HOME" reference in our
quite complex software and I think
we do not qualify as n00bs...
Any root symbol that can help derive
locations is just common sense to
us. It's not used internaly in our code
(Clojure/Java/Ruby)
but it's obviously a simple way
to bootstrap our apps and establish
On 30 June 2010 22:44, Steve Molitor wrote:
>>> the true launcher will always be the java JVM executable, and I'm
>>> not sure this is something we should really try and hide.
>
> I think it should be hidden, at least for newbies. Maven hides it - I
> invoke 'mvn' and have no idea how it invokes
> However, I don't see it helping newcomers to Clojure significantly
With respect, I'm a newcomer to Clojure, and the CLOJURE_HOME convention would
help me significantly. :-)
I think something that needs to be acknowledged is that "newcomers" and "n00bs"
are not necessarily idiots, they're just
On Jun 30, 6:45 pm, Greg wrote:
> It seems like a lot of n00b (and non-n00b) related problems have to do with
> the location of clojure.jar and clojure-contrib.jar. People generally don't
> like having to keep track of all the clojure.jars, and it would be nice if it
> was easy to switch versio
>> the true launcher will always be the java JVM executable, and I'm
>> not sure this is something we should really try and hide.
I think it should be hidden, at least for newbies. Maven hides it - I
invoke 'mvn' and have no idea how it invokes java. I don't know what jars
it puts in the classpa
JRuby uses JRUBY_HOME, which contains jruby.jar, a few other other essential
jars and gems, and any locally installed gems. (Gems are ruby's packaging
mechanism.) It also includes a jruby (jruby.bat on windows) executable
script. This script parses command line args, sets up the classpath using
J
On 30 June 2010 21:14, Brian Schlining wrote:
>>
>> >
>> > May I propose as a possible remedy CLOJURE_HOME. CLOJURE_HOME is the
>> > absolute path of a directory containing clojure.jar and possibly
>> > clojure-contrib.jar. Scripts should check if it's defined and use it
>> > instead
>> > of hard
My clj file looks like this:
#!/bin/sh
export CLASSPATH=$CLOJUREPATH:./lib/*:.:$CLASSPATH
if [ -z "$1" ]; then
exec java -server jline.ConsoleRunner clojure.main
else
SCRIPT=$(dirname $1)
export CLASSPATH=$SCRIPT/*:$SCRIPT:$CLASSPATH
exec java -server clojure.main "$1" "$@"
fi
H
>
>
> >
> > May I propose as a possible remedy CLOJURE_HOME. CLOJURE_HOME is the
> absolute path of a directory containing clojure.jar and possibly
> clojure-contrib.jar. Scripts should check if it's defined and use it instead
> of hard-coded paths, as an example, here's my clj script (in newLISP):
On 30 June 2010 18:45, Greg wrote:
> It seems like a lot of n00b (and non-n00b) related problems have to do with
> the location of clojure.jar and clojure-contrib.jar. People generally don't
> like having to keep track of all the clojure.jars, and it would be nice if it
> was easy to switch ver
It seems like a lot of n00b (and non-n00b) related problems have to do with the
location of clojure.jar and clojure-contrib.jar. People generally don't like
having to keep track of all the clojure.jars, and it would be nice if it was
easy to switch versions for scripts like clj and such.
May I
13 matches
Mail list logo
