* (defun bake (pie temp time)
"Bakes a cake for a certain amount of time, returning a cake with a new
:tastiness level."
(setf (tastiness pie)
(condp (* temp time) #'
; (LET ((#:PREDICATE2 (* TEMP TIME)) (#:EXPRESSION3 #'
Pretty cool...Clojure from the ground-up: debugging
11–20 of 22 posts
Re: Clojure from the ground-up: debugging
#12Error messages and stack traces look pretty ugly. In Common Lisp: CL-USER 51 > (bake (make-instance 'pie :flavor :blackberry) 375 10.25) Error: The value 3843.75 of #:|predicate1555| is not a predicate in CONDP. 1 (continue) Supply a new value of #:|predicate1555|. 2 (abort) Return to level 0. 3 Return to top loop level 0. A clear error message and a way to repair it. A stack frame: Call to BAKE {offset 394} PIE : #…
Re: Clojure from the ground-up: debugging
#13Error messages and stack traces look pretty ugly. In Common Lisp: CL-USER 51 > (bake (make-instance 'pie :flavor :blackberry) 375 10.25) Error: The value 3843.75 of #:|predicate1555| is not a predicate in CONDP. 1 (continue) Supply a new value of #:|predicate1555|. 2 (abort) Return to level 0. 3 Return to top loop level 0. A clear error message and a way to repair it. A stack frame: Call to BAKE {offset 394} PIE : #…
Which CL is that?
Re: Clojure from the ground-up: debugging
#14Re: Clojure from the ground-up: debugging
#15Kyle's suggestions have a ton of value, but do note that debugging Clojure(Script) can also be a pedestrian activity if you so desire. All the usual mainstream bell/whistles IDE-based interactive debugging is available today in CursiveClojure - break on all exceptions, eval in frame, etc. Also ClojureScript has had accurate source mapping in Safari, Chrome, Firefox, and Node.js for quite a long time now and recently…
Re: Clojure from the ground-up: debugging
#16Kyle's suggestions have a ton of value, but do note that debugging Clojure(Script) can also be a pedestrian activity if you so desire. All the usual mainstream bell/whistles IDE-based interactive debugging is available today in CursiveClojure - break on all exceptions, eval in frame, etc. Also ClojureScript has had accurate source mapping in Safari, Chrome, Firefox, and Node.js for quite a long time now and recently…
And if you favour open source IDEs the Eclipse based Counterclockwise http://doc.ccw-ide.org/ will provide the same debugging experience for Clojure.
Re: Clojure from the ground-up: debugging
#17I apologize for being so shallow :)
Re: Clojure from the ground-up: debugging
#18Kyle's suggestions have a ton of value, but do note that debugging Clojure(Script) can also be a pedestrian activity if you so desire. All the usual mainstream bell/whistles IDE-based interactive debugging is available today in CursiveClojure - break on all exceptions, eval in frame, etc. Also ClojureScript has had accurate source mapping in Safari, Chrome, Firefox, and Node.js for quite a long time now and recently…
And if you favour open source IDEs the Eclipse based Counterclockwise http://doc.ccw-ide.org/ will provide the same debugging experience for Clojure.
Re: Clojure from the ground-up: debugging
#19I'm trying so hard to love Clojure, but I keep running into examples of code like this in the world: http://imgur.com/79FlpTL . I don't write dense Lisp code like that, but unfortunately a lot of other people do. And I spend far more time reading code than writing it.
Re: Clojure from the ground-up: debugging
#20Kyle's suggestions have a ton of value, but do note that debugging Clojure(Script) can also be a pedestrian activity if you so desire. All the usual mainstream bell/whistles IDE-based interactive debugging is available today in CursiveClojure - break on all exceptions, eval in frame, etc. Also ClojureScript has had accurate source mapping in Safari, Chrome, Firefox, and Node.js for quite a long time now and recently…
And if you favour open source IDEs the Eclipse based Counterclockwise http://doc.ccw-ide.org/ will provide the same debugging experience for Clojure.