Scaramaccai wrote on Thursday, February 11, 2016 at 8:32 AM:
>I'm learning Clojure, and I find difficult to understand where a specific
>compiler error happens:
The stacktraces can be pretty daunting at first, unfortunately.
How are you compiling / running the code? That will have some bearing o
On Thursday, February 11, 2016 at 9:54:19 PM UTC+1, Sean Corfield wrote:
>
> Scaramaccai wrote on Thursday, February 11, 2016 at 8:32 AM:
> >I'm learning Clojure, and I find difficult to understand where a specific
> compiler error happens:
>
> The stacktraces can be pretty daunting at first,
On Friday, February 12, 2016 at 9:51:50 AM UTC+1, Scaramaccai wrote:
>
>
>
> On Thursday, February 11, 2016 at 9:54:19 PM UTC+1, Sean Corfield wrote:
>>
>> Scaramaccai wrote on Thursday, February 11, 2016 at 8:32 AM:
>> >I'm learning Clojure, and I find difficult to understand where a
>> specif
(.printStackTrace *e)
will print the full stacktrace of the most recent exception to the standard
error stream (STDERR) of the Java process.
Depending on your REPL / tooling environment, stuff printed to standard
error may not show up in your REPL. If that happens, try this:
(.printStackTrace *
Scaramaccai wrote on Friday, February 12, 2016 at 1:01 AM:
On Friday, February 12, 2016 at 9:51:50 AM UTC+1, Scaramaccai wrote:
Yes, the problem seems to be how I compiled the code. I was using
Vim+Fireplace, and doing a "cpr" (takes the content from the active buffer and
requires it inside the R
