Yes, that will fix it, but I'm not sure of the implications or why exactly
it's necessary.
I'll push it to master.
Thanks,
Ambrose
On Tue, Jan 3, 2012 at 3:55 PM, Jonas wrote:
>
>
> On Tuesday, January 3, 2012 9:45:04 AM UTC+2, Ambrose Bonnaire-Sergeant
> wrote:
>>
>> It seems if the namespace
On Tuesday, January 3, 2012 9:45:04 AM UTC+2, Ambrose Bonnaire-Sergeant
wrote:
>
> It seems if the namespace is not already loaded, then there are issues.
That's it! It's simple to fix. Just require the namespaces in the ns form.
I can send you a pull request if you want to?
/Jonas
--
Yo
Thanks for that. It seems if the namespace is not already loaded, then
there are issues. I already suspected this, and to be honest I don't know
the Compiler well enough to fully appreciate the problem.
Looking into it.
Ambrose
On Tue, Jan 3, 2012 at 3:37 PM, Jonas wrote:
> Hi,
>
> I pulled th
Hi,
I pulled the latest version.
> How are you running the code? Could you pull the latest master and try
again?
Nothing fancy:
- clone the repo
- lein deps
- start emacs, clojure-jack-in,
- compile e.g., examples/docstring -> NullPointerException
- comment out the three namespaces I mentioned
Actually, it's my environment which is the issue. Vimclojure seems to load
lots of extra libs.
It seems to be barfing at the `ns` forms.
Ambrose
On Tue, Jan 3, 2012 at 3:13 PM, Ambrose Bonnaire-Sergeant <
abonnaireserge...@gmail.com> wrote:
> Hi Jonas
>
> On Tue, Jan 3, 2012 at 2:43 PM, Jonas
Hi Jonas
On Tue, Jan 3, 2012 at 2:43 PM, Jonas wrote:
>
> 1. In order to be able to run your examples I have to comment out the
> clojure.test, clojure.stacktrace and clojure.template namespaces. Otherwise
> I get a NullPointerException[1] which I’m unable to track down. It seems to
> originate f
Hi Ambrose
I’ve been playing around with your library and find it very intresting. A
couple of questions:
1. In order to be able to run your examples I have to comment out the
clojure.test, clojure.stacktrace and clojure.template namespaces. Otherwise
I get a NullPointerException[1] which I’m
Very cool stuff Ambrose!
On Mon, Jan 2, 2012 at 1:11 PM, Scott Jaderholm wrote:
> Very cool. If you think of other potential example errors this would be
> capable of detecting it might be nice to include them in a TODO list in the
> README. This might motivate someone to implement them or devel
Very cool. If you think of other potential example errors this would be
capable of detecting it might be nice to include them in a TODO list in the
README. This might motivate someone to implement them or develop a nice
emacs UI for displaying these errors.
Scott
On Mon, Jan 2, 2012 at 4:14 AM,
Inspired by the ClojureScript compiler, analyze is an interface to the
Clojure analysis phase.
Check the README for some cool things you can do.
https://clojars.org/analyze
https://github.com/frenchy64/analyze
I've barely tested the library but it manages to analyze a good part of the
core Cloju
10 matches
Mail list logo