I found it, thanks for re-motivating me!
While preparing a minimal example I found that the error does not occur
when using cljc and clj files, it only occured when adding cljs and
lein-cljsbuild to the mix.
The "wong name" was part of the error message @Alex.
I was using lein-cljsbuild
I found it, thanks for re-motivating me!
While preparing a minimal example I found that the error does not occur
when using cljc and clj files, it only occured when adding cljs and
lein-cljsbuild to the mix.
The "wong name" was part of the error message @Alex.
I was using lein-cljsbuild 1.1.4.
I think it's unlikely that this has to do with CLJ-703. But certainly, if
you could find a version that doesn't exhibit the problem that would be
interesting.
On Saturday, January 7, 2017 at 3:11:37 PM UTC-6, Matching Socks wrote:
>
> You will eventually have to whittle it down to a minimal,
The "Reloading Clojure file" message is not coming from Clojure or
ClojureScript - that must be coming from Leiningen or a lein plugin.
Is that "wrong name" part in the actual error or is that something you
added? Again, that doesn't seem like something from the language but from
the tooling.
You will eventually have to whittle it down to a minimal, reproducible case
and file it in Jira. But if you are inclined first to entertain some wild
and irresponsible speculation, then perhaps the problem might be related to
the fix for CLJ-703, and it would work better to use the Clojure 1.7
I guess not many people are using Windows then :)
I just tried that same project on a Mac VM with case insensitive file
system, where it worked flawless.
Maybe someone has an idea how to investigate further?
Thanks,
Torsten.
Am Montag, 2. Januar 2017 11:11:42 UTC+1 schrieb Torsten Uhlmann:
>
Meikel,
Could explain your code such that somebody like me could understand it and
even play with it?
Regards,
Emeka
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
Clojure group.
To post to this group, send
On Sun, Feb 15, 2009 at 12:31 PM, Mark Volkmann
r.mark.volkm...@gmail.com wrote:
The :gen-class is only needed if you want to generate a Java class of
a certain stripe. It's not required for AOT compilation in general.
What do you mean by a certain stripe? I thought :gen-class was
needed to
Hi,
Am 13.02.2009 um 23:02 schrieb Stephen C. Gilardi:
the general case, a complete cljc program (in my opinion) would
need to:
[1] create the dest dir if it doesn't already exist
[2] launch a clojure instance with that dest dir in classpath
[3] compile
I wrote a simple cljc as a bash
On Feb 13, 2009, at 3:47 PM, Mark Volkmann wrote:
Is there a reason why it would be inadvisable or particularly
difficult to create a cljc script, short for Clojure compile, that
would take a path to a Clojure source file and compile it to .class
files? It seems tedious to have to add
On Fri, Feb 13, 2009 at 3:00 PM, Stephen C. Gilardi squee...@mac.com wrote:
On Feb 13, 2009, at 3:47 PM, Mark Volkmann wrote:
Is there a reason why it would be inadvisable or particularly
difficult to create a cljc script, short for Clojure compile, that
would take a path to a Clojure
It would perhaps be a lot more inefficient.
From what I can understand, clojure loads the namespace in question
and the actual command to the compiler is write this namespace to
here. It checks symbols from other modules and does a very light
sort of link step. This requires knowledge of other
On Feb 13, 2009, at 4:10 PM, Mark Volkmann wrote:
As far as I know, the classpath only needs clojure.jar, the src
directory and the classes directory. Here's an idea. The locations of
those could be command-line arguments to the cljc script. They could
default to simply src and classes
13 matches
Mail list logo
