--
U
--
--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clo...@googlegroups.com
Note that posts from new members are moderated - please be patient with your first post.
To unsubscribe from this group, send email to
clojure+u...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
---
You received this message because you are subscribed to the Google Groups "Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email to clojure+u...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
How do you put yourself into that mood so that you're happy/willing to program? What motivates you to do it?
--
I cannot do (set! *my-test* true)
HTH,
Jim
"Jim - FooBar();" <jimpi...@gmail.com> writes:
causes an error. What it doesn't explain is why
(set! *warn-on-reflection* true)
works just fine. Is the REPL running inside a binding? Is it possible to
add other forms of this binding? Or not? And if it is okay to use set!
And if it is okay to use set! on *warn-on-reflection*, why is it not okay to allow me, as the library developer, to define similar properties for my library which work in a similar way.
--
--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clo...@googlegroups.com
Note that posts from new members are moderated - please be patient with your first post.
To unsubscribe from this group, send email to
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
--- You received this message because you are subscribed to the Google Groups "Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscribe@googlegroups.com.
Yep, that's the problem. The library in question (https://github.com/phillord/tawny-owl) is meant to be usable by people who don't want to know that they are writing clojure.
It's useful, but scary. It mixes with laziness badly, but then, so do exceptions. It's nice, though for use in test fixtures.... (defn ontology-reasoner-fixture [tests] (binding [r/*reasoner-progress-monitor* r/reasoner-progress-monitor-silent] (tests))) for instance. This prevents the code from either poping up a GUI or generating lots of spam output, which is not good in a test.
And having established a clear use case, which appears well motivated and sensible, Clojure prevents me from providing the same convenience knobs for my own library; at least in the same way. Okay, so I can use atoms. My question, why does clojure.core not?
And which is the right default to pick? This is the problem. On my big screen, the GUI is okay. On my netbook, it's a pain. On travis, running headless, I want /dev/null.