4 ms·
Given a radical departure from the JavaScript core (comparing to Coffeescript), I wonder how easy the debugging would be.
by ivanzhao 15y ago
Given a radical departure from the JavaScript core (comparing to Coffeescript), I wonder how easy the debugging would be.
- drcode 15y agoI suspect you'll get good line number info but you'll have to deal with limitations in terms of real-time debugging (beyond having access a repl)
- devin 15y agoThis is an itch that will be scratched. Today's announcement was for an alpha release, not a polished, production-ready one.
- abi 15y agoPresumably, you wouldn't have to look at the Javascript source because the Clojurescript should directly tell what's wrong when it's compiling to Javascript. This is different from Coffee because Coffee is only a compiler front-end (a lexer/parser) and thus, doesn't really provide any execution semantics.
- jdkoeck 15y agoNo. The clojure compiler only complains about compilation errors, which doesn't help at all when you're debugging runtime errors. For clojure to be usable for serious client side development, you would definitely need a browser extension that relates the location of runtime errors in the compiled JavaScript back to the clojure source code. Which is precisely what something like GWT gives you (and more).