Oops, ignore the part about extracting the parameter name from the fn
form. I meant to delete that part, I misunderstood your problem at
first.
I say just use functions - you don't need macros here. The
boilerplate of typing "(fn [client] " multiple times is not enough to
justify their use, IMO
On May 27, 1:46 pm, nil wrote:
> I was looking
> athttp://saucelabs.com/blog/index.php/2009/12/running-your-selenium-tes...
> and in the comments, :Scott suggested that a macro could reduce some
> of the boilerplate that you see here:
>
> (def test-google
> {
> :name "google"
> :test (f
On Fri, May 27, 2011 at 1:46 PM, nil wrote:
> I was looking at
> http://saucelabs.com/blog/index.php/2009/12/running-your-selenium-tests-in-parallel-clojure/
> and in the comments, :Scott suggested that a macro could reduce some
> of the boilerplate that you see here:
>
> (def test-google
> {
>
"client" is a qualified name.
So either use "client#", but you don't want that since the macro should be
anaphoric.
The other option, which you're close to, is using "~'client", which
essentially makes "client" 'unqualified'.
Jonathan
On Fri, May 27, 2011 at 7:46 PM, nil wrote:
> I was looking
I was looking at
http://saucelabs.com/blog/index.php/2009/12/running-your-selenium-tests-in-parallel-clojure/
and in the comments, :Scott suggested that a macro could reduce some
of the boilerplate that you see here:
(def test-google
{
:name "google"
:test (fn [client]
(doto cl