On Apr 29, 2011, at 8:30 PM, Sean Bowman wrote:
> Is there any way to test code that uses clojure.contrib.condition to
> raise meaningful error messages? I've been struggling to write some
> sort of assert-expr, based on thrown-with-condition?, to check for
> these errors, b
Is there any way to test code that uses clojure.contrib.condition to
raise meaningful error messages? I've been struggling to write some
sort of assert-expr, based on thrown-with-condition?, to check for
these errors, but it's obviously way beyond my macro foo at this
point.
Thoughts,
; set up the class path)? What behaves differently if you run (require
> 'clojure.contrib.condition) in the repl and "in your program"?
Thanks for the offer of help. I decided that going monadic would be cleaner.
I'll revisit this if I turn out to be wrong.
-
Brian
2011/2/8 Brian Marick :
> The header documentation for clojure.contrib.condition says:
>
> Note: requires AOT compilation.
>
> What do I therefore do differently? How should my program text change?
The clojure-contrib jar file that your build tool - or yourself, if
you do
https://github.com/technomancy/leiningen/blob/master/sample.project.clj
try adding
:aot [clojure.contrib.condition]
to your project.clj ?
On Mon, Feb 7, 2011 at 17:56, Brian Marick wrote:
> The header documentation for clojure.contrib.condition says:
>
> Note: requires AOT co
The header documentation for clojure.contrib.condition says:
Note: requires AOT compilation.
What do I therefore do differently? How should my program text change?
Conditions seem to work in the REPL, but not in my program. I don't know if
that's due to the mysteries of AOT co
