Hi Ken,
2011/5/30 Ken Wesson <kwess...@gmail.com>:
> I get the following in "problems" in CCW when opening a particular
> Clojure project:
>
> Unable to resolve symbol: => in this context sandbox.clj
> /sandbox/src line 1 Clojure Compilation Problem
>
> The line in question is just this:
>
> (ns sandbox)
>
> Error, my left nostril. Of course, perhaps CCW is seeing the macro
> expansion, and it contains a => somewhere, and it's interpreted
> specially by more macros, but the editor isn't smart enough to realize
> that and assumes it should resolve to a global Var, but:
>
> => (macroexpand '(ns sandbox))
> (do (clojure.core/in-ns (quote sandbox))
> (clojure.core/with-loading-context
> (clojure.core/refer (quote clojure.core))))
>
> There's nothing in here that resembles => except for the REPL prompt I
> typed the macroexpand form at. I'd think maybe it was even mistaking a
> REPL prompt for a symbol in need of resolving, except it appears
> before any REPL is even started.
>
> It doesn't seem to actually break anything, though, except possibly
> AOT compilation, which I don't need for my sandbox "project" (random
> code snippets and experimentation sandbox). Unless I see this block
> AOT compilation of something that actually needs it I'm classing it as
> cosmetic. (Even if it did stop in-Eclipse AOT compilation, I'd only be
> one "lein uberjar" away from deployment anyway, so even then it isn't
> a showstopper.)
Currently, CCW is doing the following wrt problem markers (red
squiggles similar to the one you're seeing): when you start a "Clojure
Application" from the project's root node, and from them anytime you
save a file in Eclipse, an "Eclipse Clojure Builder" does a pass on
all .clj files of all "java source folders" of the project containing
the (started project/)saved file. From each of these files, it deduces
a potential lib name. E.g. from file "/src/ken_wesson/core.clj" it
will deduce a potential lib named "ken-wesson.core". Then for this
potential lib it will issue a compilation command similar to
"(clojure.core/compile 'ken-wesson.core)". Then any reported log on
stdout/stderr reported by this compilation command is parsed and will
produce a "problem marker" in Eclipse. If the reported error has a
line number, then the problem marker will appear next to this
particular line, if not, it will be placed by default on the first
line.
Does that help ?
BTW, as Meikel said, there's more chance that messages specifically
targetting CCW issues will be catched (as opposed to missed) if sent
to ccw's user mailing list:
"counterclockwise" <clojuredev-de...@googlegroups.com>
Cheers,
--
Laurent
>
> Don't know if the problem is in CCW, or the particular version of the
> Clojure compiler that installed with it, or both. The Clojure version
> at the CCW REPL reports its identity thusly:
>
> => *clojure-version*
> {:major 1, :minor 2, :incremental 0, :qualifier ""}
>
> --
> Protege: What is this seething mass of parentheses?!
> Master: Your father's Lisp REPL. This is the language of a true
> hacker. Not as clumsy or random as C++; a language for a more
> civilized age.
>
> --
> 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
--
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
