-
Notifications
You must be signed in to change notification settings - Fork 138
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cover debugging of Clojure code... #27
Comments
With a section about how to interpret Clojure stack traces. ;) |
Yes you are correct :) Also a list of common errors, with a brief explanation of the most probable causes, would help. |
There are a few exceptions mentioned in the interop guide. There will be more but within reason. |
A debug section should consider:
(func1
(func2 123)
(func3)) If I want to inspect what func2 and func3 return values look like, I can rewrite the whole form using let and do without change the final returned value and in the while checking the intermediate ones: (let [p1 (func2 123)
p2 (func3)]
(do
(println p1)
(println p2)
(func1 p1 p2)))
(func1
#_(func2 123) ; #_ comments the whole form
1000 ; forced value, which replaces the commented form
(func3)) In my opinion these sort of hints could help newbies in their coding activities. |
What helped us a lot in debugging is:
If there's any interest, I could help out with these. |
could this be done for emacs? I might consider using it(emacs) |
Things that have helped me:
|
I'm am resurrecting this site at https://clojure-doc.github.io so feel free to recreate this issue at https://github.com/clojure-doc/clojure-doc.github.io/issues or submit a PR https://github.com/clojure-doc/clojure-doc.github.io/pulls |
...depending on the used IDE / tool.
The text was updated successfully, but these errors were encountered: