@googlegroups.com
Subject: Re: Clojure (Slim 1.4.0) and Azul don't like each other
We've tracked down the problem, and it turns out to be a semantic issue around
forced vs. hinted initialization (or initialization avoidance) on explicit
class loading. It appears that Clojure make
We've tracked down the problem, and it turns out to be a semantic issue
around forced vs. hinted initialization (or initialization avoidance) on
explicit class loading. It appears that Clojure makes multiple
Class.forName() calls on the same class, with the first call intended to
avoid static i
> *From:* clojure@googlegroups.com [clojure@googlegroups.com] on behalf of
> Mark [markaddle...@gmail.com]
> *Sent:* Wednesday, June 13, 2012 3:01 PM
> *To:* clojure@googlegroups.com
> *Subject:* Re: Clojure (Slim 1.4.0) and Azul don't like each other
>
> I'm speaking fr
PM
To: clojure@googlegroups.com
Subject: Re: Clojure (Slim 1.4.0) and Azul don't like each other
I'm speaking from ignorance but this kind of error smacks of a version mismatch
between the Java runtime library and what Clojure is expecting. What version
of Java runtime are you using?
oglegroups.com
Subject: Re: Clojure (Slim 1.4.0) and Azul don't like each other
I'm speaking from ignorance but this kind of error smacks of a version mismatch
between the Java runtime library and what Clojure is expecting. What version
of Java runtime are you using? Also, is the Azul
I'm speaking from ignorance but this kind of error smacks of a version
mismatch between the Java runtime library and what Clojure is expecting.
What version of Java runtime are you using? Also, is the Azul Java library
the same as Sun's? What's the entire stacktrace?
On Wednesday, June 13, 2
