Actually, it's kinda the same (Fogus and me decided to merge trammel and
clojure-contracts into one library)
воскресенье, 3 июня 2012 г., 6:31:50 UTC+6 пользователь Sean Corfield
написал:
On Sat, Jun 2, 2012 at 5:22 PM, Vinzent ru.vinz...@gmail.com wrote:
BTW, you may want to use
On Sun, Jun 3, 2012 at 1:55 AM, Vinzent ru.vinz...@gmail.com wrote:
Actually, it's kinda the same (Fogus and me decided to merge trammel and
clojure-contracts into one library)
Yeah, I figured. I just wanted to point people to the newly created
contrib library since that's where (I assume)
Does Clojurescript have a trace function?
On Sat, Jun 2, 2012 at 5:26 PM, Softaddicts lprefonta...@softaddicts.cawrote:
clojure.tools.trace beats println by far (biased advice, I maintain
it:)))
It's also easier to segregate between debug and normal output in the code.
You can
Nvm. Not yet.
I'm reluctant to dive into clojurescript because the debugger and trace
functions aren't ready yet.
I suppose if I make test cases for everything and stick to tiny functions,
I should be alright.
Anyway, if Chris Granger uses it, it's probably pretty good.
HERE GOES!
On Sun, Jun
Not yet, I'll put this on my agenda. I need some research time not being
familiar yet with how it would translate in ClojureScript and if it's worthwhile
to implement it.
Comments from any one using ClojureScript ?
Luc
Does Clojurescript have a trace function?
On Sat, Jun 2, 2012 at 5:26
On Fri, Jun 1, 2012 at 11:18 AM, Abraham Egnor abe.eg...@gmail.com wrote:
I'm early in the process of learning clojure, and am hoping that the
community has suggestions for a frustration I've run into.
...
I eventually tracked it down by evaluating each subexpression of line - the
root bug is
On Fri, Jun 1, 2012 at 8:18 PM, Abraham Egnor abe.eg...@gmail.com wrote:
Is there some technique I'm not seeing to make this kind of simple
typo-based error less of a hassle to track down? Or is this simply a matter
of getting better at deciphering the stack traces?
I think one important
On Sat, Jun 2, 2012 at 2:34 PM, Moritz Ulrich
ulrich.mor...@googlemail.com wrote:
I think one important point here is that you use two different data
structures to hold the same kind of data.
Points and deltas are not the same kind of data. Yes, they both have
x/y/z values but their meaning is
clojure.tools.trace beats println by far (biased advice, I maintain it:)))
It's also easier to segregate between debug and normal output in the code.
You can enable/disable fn tracing dynamically from the REPL for all fns in a
given
namespace.
I seldom use a debugger. When I do it's to dive
BTW, you may want to use clojure-contracts (
https://github.com/dnaumov/clojure-contracts) instead of asserts or
:pre\:post in order to get much nicer and informative error reporting.
--
You received this message because you are subscribed to the Google
Groups Clojure group.
To post to this
On Sat, Jun 2, 2012 at 5:22 PM, Vinzent ru.vinz...@gmail.com wrote:
BTW, you may want to use clojure-contracts
(https://github.com/dnaumov/clojure-contracts) instead of asserts or
:pre\:post in order to get much nicer and informative error reporting.
Or keep an eye on
11 matches
Mail list logo
