OK, I don't know whether this is really a bug or just an obsolete message being
printed on the console, but I've reopened the ticket and added a pointer to
this discussion, and a link to exactly which commit it was that caused this
change in behavior (just before Clojure 1.5.0-RC4).
Andy
On Ma
Based on discussions I've seen on this list and clojure-dev, I think
you're using internal APIs that are not considered "supported" and
therefore subject to change at any time.
I asked about using clojure.lang.RT a while ago and was told to rely
on very little of the API, for example, so all I rel
But then(putting RT.init()),
Compiler.load() works, but Console (stderr?) says
No need to call RT.init() anymore
So I think this problem should be fixed.
2013년 3월 13일 수요일 오전 11시 32분 5초 UTC+9, Andy Fingerhut 님의 말:
> Yegor Bugayenko posted in a comment on ticket CLJ-1172 (
> http://dev.cloj
Yegor Bugayenko posted in a comment on ticket CLJ-1172 (
http://dev.clojure.org/jira/browse/CLJ-1172) that calling RT.init() before
Compiler.load() solved what looks like a similar problem for him.
Andy
On Tue, Mar 12, 2013 at 6:29 PM, Taegyoon Kim wrote:
> A new error occurred in Clojure 1.5.0
A new error occurred in Clojure 1.5.0.
(Java interop: Compiler.load(new StringReader(str));)
# Code #
import java.io.IOException;
import java.io.StringReader;
import clojure.lang.Compiler;
import clojure.lang.RT;
import clojure.lang.Var;
public class Main {
public static void main(String[]
