Sorry to revive this old thread, but I want to answer a question I had in
exactly the place I looked for the answer months ago.
On Friday, July 6, 2012 3:12:40 AM UTC-4, kovasb wrote:
On Fri, Jul 6, 2012 at 2:59 AM, David Nolen
dnolen...@gmail.comjavascript:
wrote:
On Fri, Jul 6, 2012
Nice work.
I wonder if there are similar patterns happening elsewhere, in
particular, in the part that loads libraries. Will have to take a
look.
On Wed, Jul 11, 2012 at 11:12 PM, Timothy Baldridge
tbaldri...@gmail.com wrote:
But the real issue is the stacktrace one. In this case, the bug
But the real issue is the stacktrace one. In this case, the bug could
have been found by static analysis. But in general, it can not.
I experienced this same issue and tracked it down to a bug in goog, at
least in my case.
In my case, I was making a JSON request to the server. When the
response
In this particular case it looks like read-string is failing silently,
and stopping the execution of my program.
Which to me looks like it throws an exception that gets eaten somewhere.
The odd thing is, when I evaluate the same input at the js repl in the
terminal, it works. So now there are
I found the bug in my program.
I was calling a function that didn't exist in the given namespace.
(this is called on startup)
Just to confirm, the expected behavior is that this will produce a
stacktrace in the js console?
I can try using git bisect if this is supposed to work.
On Fri, Jul 6,
The little red checkbox in the chrome developer tools would light up,
referencing the places in my compiled cljs code that blew up. It
doesn't do that anymore.
On Fri, Jul 6, 2012 at 1:35 AM, David Nolen dnolen.li...@gmail.com wrote:
Can you be more precise?
On Friday, July 6, 2012, kovas
