date:20130221


Hi all,

I''d like to have a macro like the following but preferably without the 
'eval' inside the assertion form:


(defmacro defcomponent [name co]
 (assert (component? (eval co)) Not a valid IComponent)
 `(def ~name ~co))

If I don't use eval, everything works as long as I pass a var 
in...However if I pass in something like (String. jam) it is not being 
evaluated and thus is a list not an object...and it will never satisfy 
IComponent.


any thoughts?
thanks in advance :)

Jim


--
--
You received this message because you are subscribed to the Google
Groups Clojure group.
To post to this group, send email to clojure@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+unsubscr...@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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: assertion-forms inside macros without using eval?


On 21/02/13 14:07, Jim foo.bar wrote:

Hi all,

I''d like to have a macro like the following but preferably without 
the 'eval' inside the assertion form:


(defmacro defcomponent [name co]
 (assert (component? (eval co)) Not a valid IComponent)
 `(def ~name ~co))

If I don't use eval, everything works as long as I pass a var 
in...However if I pass in something like (String. jam) it is not 
being evaluated and thus is a list not an object...and it will never 
satisfy IComponent.


any thoughts?
thanks in advance :)

Jim




I could have phrased this better...One of my arguments has to NOT be 
evaluated (name) but the other needs to be evaluated (co) so I can 
assert whatever I want to assert on it...I cannot use 'defn' (it will 
cause 'name' to be evaluated) so my only option is a macro that forces 
eval on the second arg, yes?


Jim

--
--
You received this message because you are subscribed to the Google
Groups Clojure group.
To post to this group, send email to clojure@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+unsubscr...@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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: assertion-forms inside macros without using eval?

or you could place the assert inside the backquote


On Thu, Feb 21, 2013 at 3:10 PM, Jim foo.bar jimpil1...@gmail.com wrote:

 On 21/02/13 14:07, Jim foo.bar wrote:

 Hi all,

 I''d like to have a macro like the following but preferably without the
 'eval' inside the assertion form:

 (defmacro defcomponent [name co]
  (assert (component? (eval co)) Not a valid IComponent)
  `(def ~name ~co))

 If I don't use eval, everything works as long as I pass a var
 in...However if I pass in something like (String. jam) it is not being
 evaluated and thus is a list not an object...and it will never satisfy
 IComponent.

 any thoughts?
 thanks in advance :)

 Jim



 I could have phrased this better...One of my arguments has to NOT be
 evaluated (name) but the other needs to be evaluated (co) so I can assert
 whatever I want to assert on it...I cannot use 'defn' (it will cause 'name'
 to be evaluated) so my only option is a macro that forces eval on the
 second arg, yes?


 Jim

 --
 --
 You received this message because you are subscribed to the Google
 Groups Clojure group.
 To post to this group, send email to clojure@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+unsubscribe@**googlegroups.comclojure%2bunsubscr...@googlegroups.com
 For more options, visit this group at
 http://groups.google.com/**group/clojure?hl=enhttp://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.comclojure%2bunsubscr...@googlegroups.com
 .
 For more options, visit 
 https://groups.google.com/**groups/opt_outhttps://groups.google.com/groups/opt_out
 .





-- 
Please correct me if I'm wrong or incomplete,
even if you think I'll subconsciously hate it.

-- 
-- 
You received this message because you are subscribed to the Google
Groups Clojure group.
To post to this group, send email to clojure@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+unsubscr...@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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: assertion-forms inside macros without using eval?

I tried this and it works, but I need 2 backticks and I'm essentially 
generating the assert-form when the macro is called...I'd like to 
generate only the def-form at run-time...


(defmacro defcomponent [name co]
`(assert (component? ~co) Not a valid IComponent)
  `(def ~name ~co))

it looks ugly doesn't it?

Jim



On 21/02/13 14:11, AtKaaZ wrote:

or you could place the assert inside the backquote


On Thu, Feb 21, 2013 at 3:10 PM, Jim foo.bar jimpil1...@gmail.com 
mailto:jimpil1...@gmail.com wrote:


On 21/02/13 14:07, Jim foo.bar wrote:

Hi all,

I''d like to have a macro like the following but preferably
without the 'eval' inside the assertion form:

(defmacro defcomponent [name co]
 (assert (component? (eval co)) Not a valid IComponent)
 `(def ~name ~co))

If I don't use eval, everything works as long as I pass a var
in...However if I pass in something like (String. jam) it is
not being evaluated and thus is a list not an object...and it
will never satisfy IComponent.

any thoughts?
thanks in advance :)

Jim



I could have phrased this better...One of my arguments has to NOT
be evaluated (name) but the other needs to be evaluated (co) so I
can assert whatever I want to assert on it...I cannot use 'defn'
(it will cause 'name' to be evaluated) so my only option is a
macro that forces eval on the second arg, yes?


Jim

-- 
-- 
You received this message because you are subscribed to the Google

Groups Clojure group.
To post to this group, send email to clojure@googlegroups.com
mailto:clojure@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+unsubscr...@googlegroups.com
mailto:clojure%2bunsubscr...@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+unsubscr...@googlegroups.com
mailto:clojure%2bunsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.





--
Please correct me if I'm wrong or incomplete,
even if you think I'll subconsciously hate it.

--
--
You received this message because you are subscribed to the Google
Groups Clojure group.
To post to this group, send email to clojure@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+unsubscr...@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+unsubscr...@googlegroups.com.

For more options, visit https://groups.google.com/groups/opt_out.




--
--
You received this message because you are subscribed to the Google
Groups Clojure group.
To post to this group, send email to clojure@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+unsubscr...@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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: assertion-forms inside macros without using eval?

= (def component? number?)
#'runtime.q/component?

= (defmacro defcomponent [name co]
`(do
   (assert (component? ~co) Not a valid IComponent)
   (def ~name ~co)
   )
)
#'runtime.q/defcomponent

= (defcomponent a (str a))
AssertionError Assert failed: Not a valid IComponent
(runtime.q/component? (str a))  runtime.q/eval6570 (NO_SOURCE_FILE:1)

= (defcomponent a a)
AssertionError Assert failed: Not a valid IComponent
(runtime.q/component? a)  runtime.q/eval6572 (NO_SOURCE_FILE:1)
= (defcomponent a 1)
#'runtime.q/a

= (defcomponent a (+ 1 3))
#'runtime.q/a




On Thu, Feb 21, 2013 at 3:11 PM, AtKaaZ atk...@gmail.com wrote:

 or you could place the assert inside the backquote


 On Thu, Feb 21, 2013 at 3:10 PM, Jim foo.bar jimpil1...@gmail.com wrote:

 On 21/02/13 14:07, Jim foo.bar wrote:

 Hi all,

 I''d like to have a macro like the following but preferably without the
 'eval' inside the assertion form:

 (defmacro defcomponent [name co]
  (assert (component? (eval co)) Not a valid IComponent)
  `(def ~name ~co))

 If I don't use eval, everything works as long as I pass a var
 in...However if I pass in something like (String. jam) it is not being
 evaluated and thus is a list not an object...and it will never satisfy
 IComponent.

 any thoughts?
 thanks in advance :)

 Jim



 I could have phrased this better...One of my arguments has to NOT be
 evaluated (name) but the other needs to be evaluated (co) so I can assert
 whatever I want to assert on it...I cannot use 'defn' (it will cause 'name'
 to be evaluated) so my only option is a macro that forces eval on the
 second arg, yes?


 Jim

 --
 --
 You received this message because you are subscribed to the Google
 Groups Clojure group.
 To post to this group, send email to clojure@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+unsubscribe@**googlegroups.comclojure%2bunsubscr...@googlegroups.com
 For more options, visit this group at
 http://groups.google.com/**group/clojure?hl=enhttp://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.comclojure%2bunsubscr...@googlegroups.com
 .
 For more options, visit 
 https://groups.google.com/**groups/opt_outhttps://groups.google.com/groups/opt_out
 .





 --
 Please correct me if I'm wrong or incomplete,
 even if you think I'll subconsciously hate it.




-- 
Please correct me if I'm wrong or incomplete,
even if you think I'll subconsciously hate it.

-- 
-- 
You received this message because you are subscribed to the Google
Groups Clojure group.
To post to this group, send email to clojure@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+unsubscr...@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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: assertion-forms inside macros without using eval?

that one doesn't actually work, maybe, not sure why exactly but the assert
is ignored

= (def component? number?)
#'runtime.q/component?

= (defmacro defcomponent [name co]
`(assert (component? ~co) Not a valid IComponent)
`(def ~name ~co))
#'runtime.q/defcomponent

= (defcomponent a a)
#'runtime.q/a


The `(do ...) one works though,
= (defmacro a []
 `(println 1)
 `(println 2)
 )
#'runtime.q/a
= (a)
2
nil

= (defmacro a []
 `(do
(println 1)
(println 2)
)
 )
#'runtime.q/a
= (a)
1
2
nil




On Thu, Feb 21, 2013 at 3:14 PM, Jim foo.bar jimpil1...@gmail.com wrote:

  I tried this and it works, but I need 2 backticks and I'm essentially
 generating the assert-form when the macro is called...I'd like to generate
 only the def-form at run-time...

 (defmacro defcomponent [name co]
   `(assert (component? ~co) Not a valid IComponent)
   `(def ~name ~co))

 it looks ugly doesn't it?

 Jim




 On 21/02/13 14:11, AtKaaZ wrote:

 or you could place the assert inside the backquote


 On Thu, Feb 21, 2013 at 3:10 PM, Jim foo.bar jimpil1...@gmail.com wrote:

 On 21/02/13 14:07, Jim foo.bar wrote:

 Hi all,

 I''d like to have a macro like the following but preferably without the
 'eval' inside the assertion form:

 (defmacro defcomponent [name co]
  (assert (component? (eval co)) Not a valid IComponent)
  `(def ~name ~co))

 If I don't use eval, everything works as long as I pass a var
 in...However if I pass in something like (String. jam) it is not being
 evaluated and thus is a list not an object...and it will never satisfy
 IComponent.

 any thoughts?
 thanks in advance :)

 Jim



  I could have phrased this better...One of my arguments has to NOT be
 evaluated (name) but the other needs to be evaluated (co) so I can assert
 whatever I want to assert on it...I cannot use 'defn' (it will cause 'name'
 to be evaluated) so my only option is a macro that forces eval on the
 second arg, yes?


 Jim

 --
 --
 You received this message because you are subscribed to the Google
 Groups Clojure group.
 To post to this group, send email to clojure@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+unsubscr...@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+unsubscr...@googlegroups.com.
 For more options, visit https://groups.google.com/groups/opt_out.





 --
 Please correct me if I'm wrong or incomplete,
 even if you think I'll subconsciously hate it.

  --
 --
 You received this message because you are subscribed to the Google
 Groups Clojure group.
 To post to this group, send email to clojure@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+unsubscr...@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+unsubscr...@googlegroups.com.
 For more options, visit https://groups.google.com/groups/opt_out.




  --
 --
 You received this message because you are subscribed to the Google
 Groups Clojure group.
 To post to this group, send email to clojure@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+unsubscr...@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+unsubscr...@googlegroups.com.
 For more options, visit https://groups.google.com/groups/opt_out.






-- 
Please correct me if I'm wrong or incomplete,
even if you think I'll subconsciously hate it.

-- 
-- 
You received this message because you are subscribed to the Google
Groups Clojure group.
To post to this group, send email to clojure@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+unsubscr...@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+unsubscr...@googlegroups.com.
For more options, visit

Re: assertion-forms inside macros without using eval?


aaa I see! How can I be so naive some times? ;)

Jim



On 21/02/13 14:15, AtKaaZ wrote:

= (def component? number?)
#'runtime.q/component?

= (defmacro defcomponent [name co]
`(do
   (assert (component? ~co) Not a valid IComponent)
   (def ~name ~co)
   )
)
#'runtime.q/defcomponent

= (defcomponent a (str a))
AssertionError Assert failed: Not a valid IComponent
(runtime.q/component? (str a))  runtime.q/eval6570 (NO_SOURCE_FILE:1)

= (defcomponent a a)
AssertionError Assert failed: Not a valid IComponent
(runtime.q/component? a)  runtime.q/eval6572 (NO_SOURCE_FILE:1)
= (defcomponent a 1)
#'runtime.q/a

= (defcomponent a (+ 1 3))
#'runtime.q/a




On Thu, Feb 21, 2013 at 3:11 PM, AtKaaZ atk...@gmail.com 
mailto:atk...@gmail.com wrote:


or you could place the assert inside the backquote


On Thu, Feb 21, 2013 at 3:10 PM, Jim foo.bar jimpil1...@gmail.com
mailto:jimpil1...@gmail.com wrote:

On 21/02/13 14:07, Jim foo.bar wrote:

Hi all,

I''d like to have a macro like the following but
preferably without the 'eval' inside the assertion form:

(defmacro defcomponent [name co]
 (assert (component? (eval co)) Not a valid IComponent)
 `(def ~name ~co))

If I don't use eval, everything works as long as I pass a
var in...However if I pass in something like (String.
jam) it is not being evaluated and thus is a list not an
object...and it will never satisfy IComponent.

any thoughts?
thanks in advance :)

Jim



I could have phrased this better...One of my arguments has to
NOT be evaluated (name) but the other needs to be evaluated
(co) so I can assert whatever I want to assert on it...I
cannot use 'defn' (it will cause 'name' to be evaluated) so my
only option is a macro that forces eval on the second arg, yes?


Jim

-- 
-- 
You received this message because you are subscribed to the Google

Groups Clojure group.
To post to this group, send email to clojure@googlegroups.com
mailto:clojure@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+unsubscr...@googlegroups.com
mailto:clojure%2bunsubscr...@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+unsubscr...@googlegroups.com
mailto:clojure%2bunsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.





-- 
Please correct me if I'm wrong or incomplete,

even if you think I'll subconsciously hate it.




--
Please correct me if I'm wrong or incomplete,
even if you think I'll subconsciously hate it.

--
--
You received this message because you are subscribed to the Google
Groups Clojure group.
To post to this group, send email to clojure@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+unsubscr...@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+unsubscr...@googlegroups.com.

For more options, visit https://groups.google.com/groups/opt_out.




--
--
You received this message because you are subscribed to the Google
Groups Clojure group.
To post to this group, send email to clojure@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+unsubscr...@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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: assertion-forms inside macros without using eval?


I settled for:

(defmacro defcomponent [name co]
`(let [c# ~co]
  (assert (component? c# Not a valid IComponent))
  (def ~name c#)))

Jim

On 21/02/13 14:18, AtKaaZ wrote:
that one doesn't actually work, maybe, not sure why exactly but the 
assert is ignored


= (def component? number?)
#'runtime.q/component?

= (defmacro defcomponent [name co]
`(assert (component? ~co) Not a valid IComponent)
`(def ~name ~co))
#'runtime.q/defcomponent

= (defcomponent a a)
#'runtime.q/a


The `(do ...) one works though,
= (defmacro a []
 `(println 1)
 `(println 2)
 )
#'runtime.q/a
= (a)
2
nil

= (defmacro a []
 `(do
(println 1)
(println 2)
)
 )
#'runtime.q/a
= (a)
1
2
nil




On Thu, Feb 21, 2013 at 3:14 PM, Jim foo.bar jimpil1...@gmail.com 
mailto:jimpil1...@gmail.com wrote:


I tried this and it works, but I need 2 backticks and I'm
essentially generating the assert-form when the macro is
called...I'd like to generate only the def-form at run-time...

(defmacro defcomponent [name co]
  `(assert (component? ~co) Not a valid IComponent)
  `(def ~name ~co))

it looks ugly doesn't it?

Jim




On 21/02/13 14:11, AtKaaZ wrote:

or you could place the assert inside the backquote


On Thu, Feb 21, 2013 at 3:10 PM, Jim foo.bar
jimpil1...@gmail.com mailto:jimpil1...@gmail.com wrote:

On 21/02/13 14:07, Jim foo.bar wrote:

Hi all,

I''d like to have a macro like the following but
preferably without the 'eval' inside the assertion form:

(defmacro defcomponent [name co]
 (assert (component? (eval co)) Not a valid IComponent)
 `(def ~name ~co))

If I don't use eval, everything works as long as I pass a
var in...However if I pass in something like (String.
jam) it is not being evaluated and thus is a list not
an object...and it will never satisfy IComponent.

any thoughts?
thanks in advance :)

Jim



I could have phrased this better...One of my arguments has to
NOT be evaluated (name) but the other needs to be evaluated
(co) so I can assert whatever I want to assert on it...I
cannot use 'defn' (it will cause 'name' to be evaluated) so
my only option is a macro that forces eval on the second arg,
yes?


Jim

-- 
-- 
You received this message because you are subscribed to the

Google
Groups Clojure group.
To post to this group, send email to clojure@googlegroups.com
mailto:clojure@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+unsubscr...@googlegroups.com
mailto:clojure%2bunsubscr...@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+unsubscr...@googlegroups.com
mailto:clojure%2bunsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.





-- 
Please correct me if I'm wrong or incomplete,

even if you think I'll subconsciously hate it.

-- 
-- 
You received this message because you are subscribed to the Google

Groups Clojure group.
To post to this group, send email to clojure@googlegroups.com
mailto:clojure@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+unsubscr...@googlegroups.com
mailto:clojure+unsubscr...@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+unsubscr...@googlegroups.com
mailto:clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.




-- 
-- 
You received this message because you are subscribed to the Google

Groups Clojure group.
To post to this group, send email to clojure@googlegroups.com
mailto:clojure@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+unsubscr...@googlegroups.com
mailto:clojure%2bunsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
---
You

Re: assertion-forms inside macros without using eval?

that's much better, evaluated only once, thanks.


On Thu, Feb 21, 2013 at 3:20 PM, Jim foo.bar jimpil1...@gmail.com wrote:

  I settled for:

 (defmacro defcomponent [name co]
 `(let [c# ~co]
   (assert (component? c# Not a valid IComponent))
   (def ~name c#)))

 Jim


 On 21/02/13 14:18, AtKaaZ wrote:

  that one doesn't actually work, maybe, not sure why exactly but the
 assert is ignored

 = (def component? number?)
 #'runtime.q/component?

 = (defmacro defcomponent [name co]
 `(assert (component? ~co) Not a valid IComponent)
 `(def ~name ~co))
 #'runtime.q/defcomponent

 = (defcomponent a a)
 #'runtime.q/a


  The `(do ...) one works though,
 = (defmacro a []
  `(println 1)
  `(println 2)
  )
 #'runtime.q/a
 = (a)
 2
 nil

  = (defmacro a []
  `(do
 (println 1)
 (println 2)
 )
  )
 #'runtime.q/a
 = (a)
 1
 2
 nil




 On Thu, Feb 21, 2013 at 3:14 PM, Jim foo.bar jimpil1...@gmail.com wrote:

  I tried this and it works, but I need 2 backticks and I'm essentially
 generating the assert-form when the macro is called...I'd like to generate
 only the def-form at run-time...

 (defmacro defcomponent [name co]
   `(assert (component? ~co) Not a valid IComponent)
   `(def ~name ~co))

 it looks ugly doesn't it?

 Jim




 On 21/02/13 14:11, AtKaaZ wrote:

 or you could place the assert inside the backquote


 On Thu, Feb 21, 2013 at 3:10 PM, Jim foo.bar jimpil1...@gmail.comwrote:

 On 21/02/13 14:07, Jim foo.bar wrote:

 Hi all,

 I''d like to have a macro like the following but preferably without the
 'eval' inside the assertion form:

 (defmacro defcomponent [name co]
  (assert (component? (eval co)) Not a valid IComponent)
  `(def ~name ~co))

 If I don't use eval, everything works as long as I pass a var
 in...However if I pass in something like (String. jam) it is not being
 evaluated and thus is a list not an object...and it will never satisfy
 IComponent.

 any thoughts?
 thanks in advance :)

 Jim



  I could have phrased this better...One of my arguments has to NOT be
 evaluated (name) but the other needs to be evaluated (co) so I can assert
 whatever I want to assert on it...I cannot use 'defn' (it will cause 'name'
 to be evaluated) so my only option is a macro that forces eval on the
 second arg, yes?


 Jim

 --
 --
 You received this message because you are subscribed to the Google
 Groups Clojure group.
 To post to this group, send email to clojure@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+unsubscr...@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+unsubscr...@googlegroups.com.
 For more options, visit https://groups.google.com/groups/opt_out.





 --
 Please correct me if I'm wrong or incomplete,
 even if you think I'll subconsciously hate it.

  --
 --
 You received this message because you are subscribed to the Google
 Groups Clojure group.
 To post to this group, send email to clojure@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+unsubscr...@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+unsubscr...@googlegroups.com.
 For more options, visit https://groups.google.com/groups/opt_out.




--
 --
 You received this message because you are subscribed to the Google
 Groups Clojure group.
 To post to this group, send email to clojure@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+unsubscr...@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+unsubscr...@googlegroups.com.
 For more options, visit https://groups.google.com/groups/opt_out.






 --
 Please correct me if I'm wrong or incomplete,
 even if you think I'll subconsciously hate it.

  --
 --
 You received this message because you are subscribed to the Google
 Groups Clojure group.
 To post to this group, send email to clojure@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+unsubscr...@googlegroups.com

Re: assertion-forms inside macros without using eval?


oops major typo! the correct is:

(defmacro defcomponent [name co]
`(let [c# ~co]
  (assert (component? c#) Not a valid IComponent)
  (def ~name c#)))

However, this doesn't work! Something weird with the assertion...If I 
comment it out it works as expected, otherwise the var is unbound at the 
end! strange stuffI may end up using 'eval' as I used to...


Jim


On 21/02/13 14:20, Jim foo.bar wrote:

I settled for:

(defmacro defcomponent [name co]
`(let [c# ~co]
  (assert (component? c# Not a valid IComponent))
  (def ~name c#)))

Jim

On 21/02/13 14:18, AtKaaZ wrote:
that one doesn't actually work, maybe, not sure why exactly but the 
assert is ignored


= (def component? number?)
#'runtime.q/component?

= (defmacro defcomponent [name co]
`(assert (component? ~co) Not a valid IComponent)
`(def ~name ~co))
#'runtime.q/defcomponent

= (defcomponent a a)
#'runtime.q/a


The `(do ...) one works though,
= (defmacro a []
 `(println 1)
 `(println 2)
 )
#'runtime.q/a
= (a)
2
nil

= (defmacro a []
 `(do
(println 1)
(println 2)
)
 )
#'runtime.q/a
= (a)
1
2
nil




On Thu, Feb 21, 2013 at 3:14 PM, Jim foo.bar jimpil1...@gmail.com 
mailto:jimpil1...@gmail.com wrote:


I tried this and it works, but I need 2 backticks and I'm
essentially generating the assert-form when the macro is
called...I'd like to generate only the def-form at run-time...

(defmacro defcomponent [name co]
  `(assert (component? ~co) Not a valid IComponent)
  `(def ~name ~co))

it looks ugly doesn't it?

Jim




On 21/02/13 14:11, AtKaaZ wrote:

or you could place the assert inside the backquote


On Thu, Feb 21, 2013 at 3:10 PM, Jim foo.bar
jimpil1...@gmail.com mailto:jimpil1...@gmail.com wrote:

On 21/02/13 14:07, Jim foo.bar wrote:

Hi all,

I''d like to have a macro like the following but
preferably without the 'eval' inside the assertion form:

(defmacro defcomponent [name co]
 (assert (component? (eval co)) Not a valid IComponent)
 `(def ~name ~co))

If I don't use eval, everything works as long as I pass
a var in...However if I pass in something like (String.
jam) it is not being evaluated and thus is a list not
an object...and it will never satisfy IComponent.

any thoughts?
thanks in advance :)

Jim



I could have phrased this better...One of my arguments has
to NOT be evaluated (name) but the other needs to be
evaluated (co) so I can assert whatever I want to assert on
it...I cannot use 'defn' (it will cause 'name' to be
evaluated) so my only option is a macro that forces eval on
the second arg, yes?


Jim

-- 
-- 
You received this message because you are subscribed to the

Google
Groups Clojure group.
To post to this group, send email to
clojure@googlegroups.com mailto:clojure@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+unsubscr...@googlegroups.com
mailto:clojure%2bunsubscr...@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+unsubscr...@googlegroups.com
mailto:clojure%2bunsubscr...@googlegroups.com.
For more options, visit
https://groups.google.com/groups/opt_out.





-- 
Please correct me if I'm wrong or incomplete,

even if you think I'll subconsciously hate it.

-- 
-- 
You received this message because you are subscribed to the Google

Groups Clojure group.
To post to this group, send email to clojure@googlegroups.com
mailto:clojure@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+unsubscr...@googlegroups.com
mailto:clojure+unsubscr...@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+unsubscr...@googlegroups.com
mailto:clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.




-- 
-- 
You received this message because you are subscribed to the Google

Groups Clojure group.
To post to this group,

Re: assertion-forms inside macros without using eval?

(defmacro defcomponent
  [name co]
  `(do
 (def ~name ~co)
 (set-validator! (var ~name) component?)))

Maybe like this? (Untested)

Kind regards
Meikel

-- 
-- 
You received this message because you are subscribed to the Google
Groups Clojure group.
To post to this group, send email to clojure@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+unsubscr...@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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: assertion-forms inside macros without using eval?

with eval it may not work as you expected + the double evaluation

(def component? nil?)

= (defmacro defcomponent [name co]
 (assert (component? (eval co)) Not a valid IComponent)
 `(def ~name ~co)
   )
#'runtime.q/defcomponent
= (defcomponent a (println a))
a
a
#'runtime.q/a
= (let [aa a]
   (defcomponent a (println aa))
 )
CompilerException java.lang.InstantiationException:
runtime.q$eval10641$eval10642__10643, compiling:(NO_SOURCE_PATH:2:3)

= (let [aa a]
   (defcomponent a aa)
 )
CompilerException java.lang.UnsupportedOperationException: Can't eval
locals, compiling:(NO_SOURCE_PATH:2:3)




On Thu, Feb 21, 2013 at 3:29 PM, Jim foo.bar jimpil1...@gmail.com wrote:

  oops major typo! the correct is:


 (defmacro defcomponent [name co]
 `(let [c# ~co]
   (assert (component? c#) Not a valid IComponent)
   (def ~name c#)))

 However, this doesn't work! Something weird with the assertion...If I
 comment it out it works as expected, otherwise the var is unbound at the
 end! strange stuffI may end up using 'eval' as I used to...

 Jim



 On 21/02/13 14:20, Jim foo.bar wrote:

 I settled for:

 (defmacro defcomponent [name co]
 `(let [c# ~co]
   (assert (component? c# Not a valid IComponent))
   (def ~name c#)))

 Jim

 On 21/02/13 14:18, AtKaaZ wrote:

  that one doesn't actually work, maybe, not sure why exactly but the
 assert is ignored

 = (def component? number?)
 #'runtime.q/component?

 = (defmacro defcomponent [name co]
 `(assert (component? ~co) Not a valid IComponent)
 `(def ~name ~co))
 #'runtime.q/defcomponent

 = (defcomponent a a)
 #'runtime.q/a


  The `(do ...) one works though,
 = (defmacro a []
  `(println 1)
  `(println 2)
  )
 #'runtime.q/a
 = (a)
 2
 nil

  = (defmacro a []
  `(do
 (println 1)
 (println 2)
 )
  )
 #'runtime.q/a
 = (a)
 1
 2
 nil




 On Thu, Feb 21, 2013 at 3:14 PM, Jim foo.bar jimpil1...@gmail.com wrote:

  I tried this and it works, but I need 2 backticks and I'm essentially
 generating the assert-form when the macro is called...I'd like to generate
 only the def-form at run-time...

 (defmacro defcomponent [name co]
   `(assert (component? ~co) Not a valid IComponent)
   `(def ~name ~co))

 it looks ugly doesn't it?

 Jim




 On 21/02/13 14:11, AtKaaZ wrote:

 or you could place the assert inside the backquote


 On Thu, Feb 21, 2013 at 3:10 PM, Jim foo.bar jimpil1...@gmail.comwrote:

 On 21/02/13 14:07, Jim foo.bar wrote:

 Hi all,

 I''d like to have a macro like the following but preferably without the
 'eval' inside the assertion form:

 (defmacro defcomponent [name co]
  (assert (component? (eval co)) Not a valid IComponent)
  `(def ~name ~co))

 If I don't use eval, everything works as long as I pass a var
 in...However if I pass in something like (String. jam) it is not being
 evaluated and thus is a list not an object...and it will never satisfy
 IComponent.

 any thoughts?
 thanks in advance :)

 Jim



  I could have phrased this better...One of my arguments has to NOT be
 evaluated (name) but the other needs to be evaluated (co) so I can assert
 whatever I want to assert on it...I cannot use 'defn' (it will cause 'name'
 to be evaluated) so my only option is a macro that forces eval on the
 second arg, yes?


 Jim

 --
 --
 You received this message because you are subscribed to the Google
 Groups Clojure group.
 To post to this group, send email to clojure@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+unsubscr...@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+unsubscr...@googlegroups.com.
 For more options, visit https://groups.google.com/groups/opt_out.





 --
 Please correct me if I'm wrong or incomplete,
 even if you think I'll subconsciously hate it.

  --
 --
 You received this message because you are subscribed to the Google
 Groups Clojure group.
 To post to this group, send email to clojure@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+unsubscr...@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+unsubscr...@googlegroups.com.
 For more options, visit https://groups.google.com/groups/opt_out.




--
 --
 You received this message because you are subscribed to the Google
 Groups Clojure group.
 To post to this group, send email to clojure@googlegroups.com

Creating a hash-map with conditional keys

Hello,

I am trying to figure out how to make the following elegantly in clojure. 

I have a hash-map which has some key-value pairs and I would like to append 
to that hash-map a couple more key-value pairs IF some specific condition 
is met. For example, the create-map creates the main hash-map but i would 
like *to merge* the map with the value returned from create-key-value, if 
the condition inside that function is met.

(defn create-key-value [value] 

 (when (some-condition-true) {:extra-key extra-value)) 

 

 (defn create-map [] 

{:foo a

 :bar b}) 


The final, merged, map should look like this *if* create-key-value returned 
the :extra-key

{:foo a, :bar b, :extra-key extra-value}


...or if it didn't to return this:
 

  {:foo a, :bar b}


I did find a proposed solution on a stackoverflow 
posthttp://stackoverflow.com/questions/8992997/initializing-elements-of-a-map-conditionally-in-clojure,
 
but I am not sure if that's the most elegant way. 

Thank you for your time.

Regards,

Ryan

-- 
-- 
You received this message because you are subscribed to the Google
Groups Clojure group.
To post to this group, send email to clojure@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+unsubscr...@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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: assertion-forms inside macros without using eval?

I think the assert is working but either something eats up the thrown
exception silently which would explain why def isn't reached, OR the
defcomponent is never called, OR it is called with a different name param
as you'd have expected. Try putting something before the assert to log if
that point was ever reached.


On Thu, Feb 21, 2013 at 3:29 PM, Jim foo.bar jimpil1...@gmail.com wrote:

  oops major typo! the correct is:


 (defmacro defcomponent [name co]
 `(let [c# ~co]
   (assert (component? c#) Not a valid IComponent)
   (def ~name c#)))

 However, this doesn't work! Something weird with the assertion...If I
 comment it out it works as expected, otherwise the var is unbound at the
 end! strange stuffI may end up using 'eval' as I used to...

 Jim



 On 21/02/13 14:20, Jim foo.bar wrote:

 I settled for:

 (defmacro defcomponent [name co]
 `(let [c# ~co]
   (assert (component? c# Not a valid IComponent))
   (def ~name c#)))

 Jim

 On 21/02/13 14:18, AtKaaZ wrote:

  that one doesn't actually work, maybe, not sure why exactly but the
 assert is ignored

 = (def component? number?)
 #'runtime.q/component?

 = (defmacro defcomponent [name co]
 `(assert (component? ~co) Not a valid IComponent)
 `(def ~name ~co))
 #'runtime.q/defcomponent

 = (defcomponent a a)
 #'runtime.q/a


  The `(do ...) one works though,
 = (defmacro a []
  `(println 1)
  `(println 2)
  )
 #'runtime.q/a
 = (a)
 2
 nil

  = (defmacro a []
  `(do
 (println 1)
 (println 2)
 )
  )
 #'runtime.q/a
 = (a)
 1
 2
 nil




 On Thu, Feb 21, 2013 at 3:14 PM, Jim foo.bar jimpil1...@gmail.com wrote:

  I tried this and it works, but I need 2 backticks and I'm essentially
 generating the assert-form when the macro is called...I'd like to generate
 only the def-form at run-time...

 (defmacro defcomponent [name co]
   `(assert (component? ~co) Not a valid IComponent)
   `(def ~name ~co))

 it looks ugly doesn't it?

 Jim




 On 21/02/13 14:11, AtKaaZ wrote:

 or you could place the assert inside the backquote


 On Thu, Feb 21, 2013 at 3:10 PM, Jim foo.bar jimpil1...@gmail.comwrote:

 On 21/02/13 14:07, Jim foo.bar wrote:

 Hi all,

 I''d like to have a macro like the following but preferably without the
 'eval' inside the assertion form:

 (defmacro defcomponent [name co]
  (assert (component? (eval co)) Not a valid IComponent)
  `(def ~name ~co))

 If I don't use eval, everything works as long as I pass a var
 in...However if I pass in something like (String. jam) it is not being
 evaluated and thus is a list not an object...and it will never satisfy
 IComponent.

 any thoughts?
 thanks in advance :)

 Jim



  I could have phrased this better...One of my arguments has to NOT be
 evaluated (name) but the other needs to be evaluated (co) so I can assert
 whatever I want to assert on it...I cannot use 'defn' (it will cause 'name'
 to be evaluated) so my only option is a macro that forces eval on the
 second arg, yes?


 Jim

 --
 --
 You received this message because you are subscribed to the Google
 Groups Clojure group.
 To post to this group, send email to clojure@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+unsubscr...@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+unsubscr...@googlegroups.com.
 For more options, visit https://groups.google.com/groups/opt_out.





 --
 Please correct me if I'm wrong or incomplete,
 even if you think I'll subconsciously hate it.

  --
 --
 You received this message because you are subscribed to the Google
 Groups Clojure group.
 To post to this group, send email to clojure@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+unsubscr...@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+unsubscr...@googlegroups.com.
 For more options, visit https://groups.google.com/groups/opt_out.




--
 --
 You received this message because you are subscribed to the Google
 Groups Clojure group.
 To post to this group, send email to clojure@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+unsubscr...@googlegroups.com
 For more options, visit this group at
 http://groups.google.com/group/clojure?hl=en
 ---
 You received this message because you are

Re: assertion-forms inside macros without using eval?


Hi Meikel,

This seems to work but returns nil and so you can't see that a new var 
has been defined!


cluja.core= (defcomponent maxent-person maxent)
nil
cluja.core= maxent-person ;;was it defined?
#NameFinderME opennlp.tools.namefind.NameFinderME@2019666a ;;yes it was!

Jim


On 21/02/13 14:42, Meikel Brandmeyer (kotarak) wrote:

(defmacro defcomponent
  [name co]
  `(do
 (def ~name ~co)
 (set-validator! (var ~name) component?)))

Maybe like this? (Untested)

Kind regards
Meikel

--
--
You received this message because you are subscribed to the Google
Groups Clojure group.
To post to this group, send email to clojure@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+unsubscr...@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+unsubscr...@googlegroups.com.

For more options, visit https://groups.google.com/groups/opt_out.




--
--
You received this message because you are subscribed to the Google
Groups Clojure group.
To post to this group, send email to clojure@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+unsubscr...@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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: assertion-forms inside macros without using eval?

Then simply add a (var ~name) as last statement in the do.

Kind regards
Meikel

-- 
-- 
You received this message because you are subscribed to the Google
Groups Clojure group.
To post to this group, send email to clojure@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+unsubscr...@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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: assertion-forms inside macros without using eval?

Yes you're right, this does the trick...However now I've ended up 
unquoting 'name' 3 times! I'm pretty sure this not a good practice in 
general, is it? On the other hand I cannot use 'gensym' cos I want the 
name intact or later access...hmmm...I never expected this would be so 
confusing!


Jim


On 21/02/13 14:52, Meikel Brandmeyer (kotarak) wrote:

Then simply add a (var ~name) as last statement in the do.

Kind regards
Meikel

--
--
You received this message because you are subscribed to the Google
Groups Clojure group.
To post to this group, send email to clojure@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+unsubscr...@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+unsubscr...@googlegroups.com.

For more options, visit https://groups.google.com/groups/opt_out.




--
--
You received this message because you are subscribed to the Google
Groups Clojure group.
To post to this group, send email to clojure@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+unsubscr...@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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: assertion-forms inside macros without using eval?

Moreover, now the exception thrown when the validation fails is not very 
informative!


IllegalStateException Invalid reference state clojure.lang.ARef.validate 
(ARef.java:33)


assert let's you speciy the message you want that is why I preferred it...

Jim





On 21/02/13 14:56, Jim foo.bar wrote:
Yes you're right, this does the trick...However now I've ended up 
unquoting 'name' 3 times! I'm pretty sure this not a good practice in 
general, is it? On the other hand I cannot use 'gensym' cos I want the 
name intact or later access...hmmm...I never expected this would be so 
confusing!


Jim


On 21/02/13 14:52, Meikel Brandmeyer (kotarak) wrote:

Then simply add a (var ~name) as last statement in the do.

Kind regards
Meikel

--
--
You received this message because you are subscribed to the Google
Groups Clojure group.
To post to this group, send email to clojure@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+unsubscr...@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+unsubscr...@googlegroups.com.

For more options, visit https://groups.google.com/groups/opt_out.






--
--
You received this message because you are subscribed to the Google
Groups Clojure group.
To post to this group, send email to clojure@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+unsubscr...@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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Creating a hash-map with conditional keys

Hi,

merge works with nil. So (merge (create-map) (create-key-value 
some-value)) should work as you intend with the functions as they are 
defined now.

Kind regards
Meikel

-- 
-- 
You received this message because you are subscribed to the Google
Groups Clojure group.
To post to this group, send email to clojure@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+unsubscr...@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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: assertion-forms inside macros without using eval?

this is what i'd use

(def component? number?)

*(defmacro defcomponent [name co]
  `(let [c# ~co]
 (assert (component? c#)
   (str Not a valid IComponent passed:\nevaluated form: `
 (pr-str c#) `\noriginal form: `
 '~co `\nfull form: ` '~form `
 \nlocation:  ~(meta form)  file:  ~*file*
 ))
 (def ~name c#)
 )
  )*
= *assert*
true
= (defcomponent a (do a (str b)))
AssertionError Assert failed: Not a valid IComponent passed:
evaluated form: `b`
original form: `(do a (str b))`
full form: `(defcomponent a (do a (str b)))`
location: {:column 1, :line 96} file: util\funxions.clj
(util.funxions/component? c__33004__auto__)  util.funxions/eval33010
(funxions.clj:96)


(defcomponent a (do a (str b)))
=* (defcomponent a (+ 1 2))*
#'runtime.q/a
= a
3




On Thu, Feb 21, 2013 at 3:51 PM, AtKaaZ atk...@gmail.com wrote:

 I think the assert is working but either something eats up the thrown
 exception silently which would explain why def isn't reached, OR the
 defcomponent is never called, OR it is called with a different name param
 as you'd have expected. Try putting something before the assert to log if
 that point was ever reached.


 On Thu, Feb 21, 2013 at 3:29 PM, Jim foo.bar jimpil1...@gmail.com wrote:

  oops major typo! the correct is:


 (defmacro defcomponent [name co]
 `(let [c# ~co]
   (assert (component? c#) Not a valid IComponent)
   (def ~name c#)))

 However, this doesn't work! Something weird with the assertion...If I
 comment it out it works as expected, otherwise the var is unbound at the
 end! strange stuffI may end up using 'eval' as I used to...

 Jim



 On 21/02/13 14:20, Jim foo.bar wrote:

 I settled for:

 (defmacro defcomponent [name co]
 `(let [c# ~co]
   (assert (component? c# Not a valid IComponent))
   (def ~name c#)))

 Jim

 On 21/02/13 14:18, AtKaaZ wrote:

  that one doesn't actually work, maybe, not sure why exactly but the
 assert is ignored

 = (def component? number?)
 #'runtime.q/component?

 = (defmacro defcomponent [name co]
 `(assert (component? ~co) Not a valid IComponent)
 `(def ~name ~co))
 #'runtime.q/defcomponent

 = (defcomponent a a)
 #'runtime.q/a


  The `(do ...) one works though,
 = (defmacro a []
  `(println 1)
  `(println 2)
  )
 #'runtime.q/a
 = (a)
 2
 nil

  = (defmacro a []
  `(do
 (println 1)
 (println 2)
 )
  )
 #'runtime.q/a
 = (a)
 1
 2
 nil




 On Thu, Feb 21, 2013 at 3:14 PM, Jim foo.bar jimpil1...@gmail.comwrote:

  I tried this and it works, but I need 2 backticks and I'm essentially
 generating the assert-form when the macro is called...I'd like to generate
 only the def-form at run-time...

 (defmacro defcomponent [name co]
   `(assert (component? ~co) Not a valid IComponent)
   `(def ~name ~co))

 it looks ugly doesn't it?

 Jim




 On 21/02/13 14:11, AtKaaZ wrote:

 or you could place the assert inside the backquote


 On Thu, Feb 21, 2013 at 3:10 PM, Jim foo.bar jimpil1...@gmail.comwrote:

 On 21/02/13 14:07, Jim foo.bar wrote:

 Hi all,

 I''d like to have a macro like the following but preferably without
 the 'eval' inside the assertion form:

 (defmacro defcomponent [name co]
  (assert (component? (eval co)) Not a valid IComponent)
  `(def ~name ~co))

 If I don't use eval, everything works as long as I pass a var
 in...However if I pass in something like (String. jam) it is not being
 evaluated and thus is a list not an object...and it will never satisfy
 IComponent.

 any thoughts?
 thanks in advance :)

 Jim



  I could have phrased this better...One of my arguments has to NOT be
 evaluated (name) but the other needs to be evaluated (co) so I can assert
 whatever I want to assert on it...I cannot use 'defn' (it will cause 'name'
 to be evaluated) so my only option is a macro that forces eval on the
 second arg, yes?


 Jim

 --
 --
 You received this message because you are subscribed to the Google
 Groups Clojure group.
 To post to this group, send email to clojure@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+unsubscr...@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+unsubscr...@googlegroups.com.
 For more options, visit https://groups.google.com/groups/opt_out.





 --
 Please correct me if I'm wrong or incomplete,
 even if you think I'll subconsciously hate it.

  --
 --
 You received this message because you are subscribed to the Google
 Groups Clojure group.
 To post to this group, send email to clojure@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

Re: assertion-forms inside macros without using eval?


I apologise...this works almost perfectly:

(defmacro defcomponent [name co]
`(let [c# ~co]
  (assert (component? c#) Not a valid IComponent)
  (def ~name c#)))

the only slight problem is the error thrown which has the gensym symbol 
in the flailing condition...Well, I can't have everything can I? :)


Jim

On 21/02/13 14:51, AtKaaZ wrote:
I think the assert is working but either something eats up the thrown 
exception silently which would explain why def isn't reached, OR the 
defcomponent is never called, OR it is called with a different name 
param as you'd have expected. Try putting something before the assert 
to log if that point was ever reached.



On Thu, Feb 21, 2013 at 3:29 PM, Jim foo.bar jimpil1...@gmail.com 
mailto:jimpil1...@gmail.com wrote:


oops major typo! the correct is:


(defmacro defcomponent [name co]
`(let [c# ~co]
  (assert (component? c#) Not a valid IComponent)
  (def ~name c#)))

However, this doesn't work! Something weird with the
assertion...If I comment it out it works as expected, otherwise
the var is unbound at the end! strange stuffI may end up using
'eval' as I used to...

Jim



On 21/02/13 14:20, Jim foo.bar wrote:

I settled for:

(defmacro defcomponent [name co]
`(let [c# ~co]
  (assert (component? c# Not a valid IComponent))
  (def ~name c#)))

Jim

On 21/02/13 14:18, AtKaaZ wrote:

that one doesn't actually work, maybe, not sure why exactly but
the assert is ignored

= (def component? number?)
#'runtime.q/component?

= (defmacro defcomponent [name co]
`(assert (component? ~co) Not a valid IComponent)
`(def ~name ~co))
#'runtime.q/defcomponent

= (defcomponent a a)
#'runtime.q/a


The `(do ...) one works though,
= (defmacro a []
 `(println 1)
 `(println 2)
 )
#'runtime.q/a
= (a)
2
nil

= (defmacro a []
 `(do
(println 1)
(println 2)
)
 )
#'runtime.q/a
= (a)
1
2
nil




On Thu, Feb 21, 2013 at 3:14 PM, Jim foo.bar
jimpil1...@gmail.com mailto:jimpil1...@gmail.com wrote:

I tried this and it works, but I need 2 backticks and I'm
essentially generating the assert-form when the macro is
called...I'd like to generate only the def-form at run-time...

(defmacro defcomponent [name co]
  `(assert (component? ~co) Not a valid IComponent)
  `(def ~name ~co))

it looks ugly doesn't it?

Jim




On 21/02/13 14:11, AtKaaZ wrote:

or you could place the assert inside the backquote


On Thu, Feb 21, 2013 at 3:10 PM, Jim foo.bar
jimpil1...@gmail.com mailto:jimpil1...@gmail.com wrote:

On 21/02/13 14:07, Jim foo.bar wrote:

Hi all,

I''d like to have a macro like the following but
preferably without the 'eval' inside the assertion
form:

(defmacro defcomponent [name co]
 (assert (component? (eval co)) Not a valid
IComponent)
 `(def ~name ~co))

If I don't use eval, everything works as long as I
pass a var in...However if I pass in something like
(String. jam) it is not being evaluated and thus
is a list not an object...and it will never satisfy
IComponent.

any thoughts?
thanks in advance :)

Jim



I could have phrased this better...One of my arguments
has to NOT be evaluated (name) but the other needs to
be evaluated (co) so I can assert whatever I want to
assert on it...I cannot use 'defn' (it will cause
'name' to be evaluated) so my only option is a macro
that forces eval on the second arg, yes?


Jim

-- 
-- 
You received this message because you are subscribed to

the Google
Groups Clojure group.
To post to this group, send email to
clojure@googlegroups.com mailto:clojure@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+unsubscr...@googlegroups.com
mailto:clojure%2bunsubscr...@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+unsubscr...@googlegroups.com
mailto:clojure%2bunsubscr...@googlegroups.com.

Re: assertion-forms inside macros without using eval?

Hi,

Am Donnerstag, 21. Februar 2013 16:08:36 UTC+1 schrieb Jim foo.bar:

  I apologise...this works almost perfectly:

 (defmacro defcomponent [name co]
 `(let [c# ~co]  
   (assert (component? c#) Not a valid IComponent)
   (def ~name c#)))

 the only slight problem is the error thrown which has the gensym symbol in 
 the flailing condition...Well, I can't have everything can I? :)


(defmacro defcomponent [name co]
  `(do
 (def ~name)
 (let [c# ~co]
   (assert (component? c#) Not a valid IComponent)
   (alter-var-root! (var ~name) (constantly c#)))
 (var ~name

Since name is an argument to def it can only ever be a literal symbol.

Kind regards
Meikel

-- 
-- 
You received this message because you are subscribed to the Google
Groups Clojure group.
To post to this group, send email to clojure@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+unsubscr...@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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Creating a hash-map with conditional keys

Thanks Meikel for your reply.

It wasn't clear on my example, but I wish to use *merge *inside my 
create-map function. Do you think I should bind my hash-map to a let 
variable first and then apply merge, or do you have another proposal? What 
i mean is this:

(defn create-key-value [value] 

 (when (some-condition-true) {:extra-key value)) 


(defn create-map [] 
   (let [my-map {:foo a :bar b}]
 (merge my-map (create-key-value some-value)))


Is the above clojurish or is there a better way? For example if the 
my-map was a big hash-map, and not with just two pairs, wouldn't it be ugly 
with the above way? or..it's just fine and no better way is possible?

Ryan 

On Thursday, February 21, 2013 5:02:21 PM UTC+2, Meikel Brandmeyer 
(kotarak) wrote:

 Hi,

 merge works with nil. So (merge (create-map) (create-key-value 
 some-value)) should work as you intend with the functions as they are 
 defined now.

 Kind regards
 Meikel



-- 
-- 
You received this message because you are subscribed to the Google
Groups Clojure group.
To post to this group, send email to clojure@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+unsubscr...@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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: a bit mystified by unchecked-multiply

2013-02-21 Thread John Lawrence Aspden

Great, thanks!

So if one is an object and one is a primitive is one of these not true?

user= (type seed1) 
java.lang.Long 
user= (type 25214903917) 
java.lang.Long 

Cheers, John.





On Wednesday, February 20, 2013 11:44:44 PM UTC, Herwig Hochleitner wrote:

 I agree that unchecked-multiply should do an unchecked multiply, even when 
 faced with objects. Going to bring that up on clojure-dev.

 A workaround: (unchecked-multiply (long seed1) 0x5DEECE66D)



-- 
-- 
You received this message because you are subscribed to the Google
Groups Clojure group.
To post to this group, send email to clojure@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+unsubscr...@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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Creating a hash-map with conditional keys

I'd often just write it like this:

(defn create-map []
   (merge {:foo a
:bar b
... many more keys}
   (when (some-condition-true)
  {:extra-key value)))


Alex

On Thu, Feb 21, 2013 at 7:27 AM, Ryan arekand...@gmail.com wrote:

 Thanks Meikel for your reply.

 It wasn't clear on my example, but I wish to use *merge *inside my
 create-map function. Do you think I should bind my hash-map to a let
 variable first and then apply merge, or do you have another proposal? What
 i mean is this:

 (defn create-key-value [value]

  (when (some-condition-true) {:extra-key value))


 (defn create-map []
   (let [my-map {:foo a :bar b}]
 (merge my-map (create-key-value some-value)))


 Is the above clojurish or is there a better way? For example if the
 my-map was a big hash-map, and not with just two pairs, wouldn't it be ugly
 with the above way? or..it's just fine and no better way is possible?

 Ryan

 On Thursday, February 21, 2013 5:02:21 PM UTC+2, Meikel Brandmeyer
 (kotarak) wrote:

 Hi,

 merge works with nil. So (merge (create-map) (create-key-value
 some-value)) should work as you intend with the functions as they are
 defined now.

 Kind regards
 Meikel

  --
 --
 You received this message because you are subscribed to the Google
 Groups Clojure group.
 To post to this group, send email to clojure@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+unsubscr...@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+unsubscr...@googlegroups.com.
 For more options, visit https://groups.google.com/groups/opt_out.




-- 
-- 
You received this message because you are subscribed to the Google
Groups Clojure group.
To post to this group, send email to clojure@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+unsubscr...@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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Creating a hash-map with conditional keys

Another alternative way, added in Clojure 1.5, can be nice if you have a
lot of conditionally-added key-value pairs:

(defn create-map []
   (cond- {:base :map}
   (pred1) (assoc :extra-key1 value)
   (pred2) (assoc :extra-key2 value)
   (pred3) (assoc :extra-key3 value)
   (pred4) (assoc :extra-key4 value)))


On Thu, Feb 21, 2013 at 7:41 AM, Alex Baranosky 
alexander.barano...@gmail.com wrote:

 I'd often just write it like this:

 (defn create-map []
   (merge {:foo a
:bar b
... many more keys}
   (when (some-condition-true)
  {:extra-key value)))


 Alex


 On Thu, Feb 21, 2013 at 7:27 AM, Ryan arekand...@gmail.com wrote:

 Thanks Meikel for your reply.

 It wasn't clear on my example, but I wish to use *merge *inside my
 create-map function. Do you think I should bind my hash-map to a let
 variable first and then apply merge, or do you have another proposal? What
 i mean is this:

 (defn create-key-value [value]

  (when (some-condition-true) {:extra-key value))


 (defn create-map []
   (let [my-map {:foo a :bar b}]
 (merge my-map (create-key-value some-value)))


 Is the above clojurish or is there a better way? For example if the
 my-map was a big hash-map, and not with just two pairs, wouldn't it be ugly
 with the above way? or..it's just fine and no better way is possible?

 Ryan

 On Thursday, February 21, 2013 5:02:21 PM UTC+2, Meikel Brandmeyer
 (kotarak) wrote:

 Hi,

 merge works with nil. So (merge (create-map) (create-key-value
 some-value)) should work as you intend with the functions as they are
 defined now.

 Kind regards
 Meikel

  --
 --
 You received this message because you are subscribed to the Google
 Groups Clojure group.
 To post to this group, send email to clojure@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+unsubscr...@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+unsubscr...@googlegroups.com.
 For more options, visit https://groups.google.com/groups/opt_out.






-- 
-- 
You received this message because you are subscribed to the Google
Groups Clojure group.
To post to this group, send email to clojure@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+unsubscr...@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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Creating a hash-map with conditional keys

Thanks for your input Alex.

Do you think a macro would be appropriate if I use this more than once in 
my code?

Ryan

On Thursday, February 21, 2013 5:41:49 PM UTC+2, Alex Baranosky wrote:

 I'd often just write it like this:

 (defn create-map []
   (merge {:foo a
:bar b
... many more keys}
   (when (some-condition-true)
  {:extra-key value)))


 Alex

 On Thu, Feb 21, 2013 at 7:27 AM, Ryan areka...@gmail.com javascript:wrote:

 Thanks Meikel for your reply.

 It wasn't clear on my example, but I wish to use *merge *inside my 
 create-map function. Do you think I should bind my hash-map to a let 
 variable first and then apply merge, or do you have another proposal? What 
 i mean is this:

 (defn create-key-value [value] 

  (when (some-condition-true) {:extra-key value)) 


 (defn create-map [] 
   (let [my-map {:foo a :bar b}]
 (merge my-map (create-key-value some-value)))


 Is the above clojurish or is there a better way? For example if the 
 my-map was a big hash-map, and not with just two pairs, wouldn't it be ugly 
 with the above way? or..it's just fine and no better way is possible?

 Ryan 

 On Thursday, February 21, 2013 5:02:21 PM UTC+2, Meikel Brandmeyer 
 (kotarak) wrote:

 Hi,

 merge works with nil. So (merge (create-map) (create-key-value 
 some-value)) should work as you intend with the functions as they are 
 defined now.

 Kind regards
 Meikel

  -- 
 -- 
 You received this message because you are subscribed to the Google
 Groups Clojure group.
 To post to this group, send email to clo...@googlegroups.comjavascript:
 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 javascript:
 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 javascript:.
 For more options, visit https://groups.google.com/groups/opt_out.
  
  




-- 
-- 
You received this message because you are subscribed to the Google
Groups Clojure group.
To post to this group, send email to clojure@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+unsubscr...@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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Bumi, a project for loading a git repo into a Titan graph database

2013-02-21 Thread Zack Maril

https://github.com/zmaril/bumi

Bumi loads a git repo into a Titan graph database[0]. You can then ask 
questions about the history of the project with Faunus[1]. I've 
successfully loaded the Linux kernel onto an AWS instance. I'm working now 
to start asking good questions and see if I can't find out anything neat. 
Any suggestions about paths of investigation to pursue would fall on open 
ears. I'm open sourcing this now in case anybody wants to play around with 
it. In theory, it should work with any git repo. In practice, I've only 
tested it on the Linux kernel so far. It's written in Clojure, using 
Hermes[2]. 

-Zack

[0] http://thinkaurelius.github.com/titan/ 
[1] http://thinkaurelius.github.com/faunus/
[2] https://github.com/gameclosure/hermes

-- 
-- 
You received this message because you are subscribed to the Google
Groups Clojure group.
To post to this group, send email to clojure@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+unsubscr...@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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: assertion-forms inside macros without using eval?

I'd actually use this myself:

;the following is inspired from
http://blog.jayfields.com/2011/02/clojure-and.html
(defmacro get-lexical-env []

= (let [a 1 b (+ 1 2)]
 (let [c (do \a\ \b\)]
   (q/get-lexical-env)
   )
 )
{a 1, b 3, c \b\}

  (let [envkeys (keys env)]
`(zipmap (quote ~envkeys) (list ~@envkeys))
)
  )

(defmacro show-lexical-env []
  `(prn (get-lexical-env))
  )


(def component? number?)

(defmacro defcomponent [name co]
  `(let [c# ~co]
 (assert (component? c#)
   (str Not a valid IComponent passed:\nevaluated form: `
 (pr-str c#) `\noriginal form: `
 '~co `\nfull form: ` '~form `
 \nlocation:  ~(meta form)  file:  ~*file*
 \ncurrent lexical env:  (get-lexical-env)
 \n
 ))
 (def ~name c#)
 )
  )

(defcomponent a (do a (str b)))

AssertionError Assert failed: Not a valid IComponent passed:
evaluated form: `b`
original form: `(do a (str b))`
full form: `(defcomponent a (do a (str b)))`
location: {:column 1, :line 17} file: NO_SOURCE_PATH
current lexical env: {c__38734__auto__ b}

(util.funxions/component? c__38734__auto__)  util.funxions/eval38740
(NO_SOURCE_FILE:17)




On Thu, Feb 21, 2013 at 4:08 PM, AtKaaZ atk...@gmail.com wrote:

 this is what i'd use

 (def component? number?)

 *
 (defmacro defcomponent [name co]
   `(let [c# ~co]
  (assert (component? c#)
(str Not a valid IComponent passed:\nevaluated form: `
  (pr-str c#) `\noriginal form: `
  '~co `\nfull form: ` '~form `
  \nlocation:  ~(meta form)  file:  ~*file*
  ))
  (def ~name c#)
  )
   )*
 = *assert*
 true
 = (defcomponent a (do a (str b)))
 AssertionError Assert failed: Not a valid IComponent passed:
 evaluated form: `b`
 original form: `(do a (str b))`
 full form: `(defcomponent a (do a (str b)))`
 location: {:column 1, :line 96} file: util\funxions.clj
 (util.funxions/component? c__33004__auto__)  util.funxions/eval33010
 (funxions.clj:96)


 (defcomponent a (do a (str b)))
 =* (defcomponent a (+ 1 2))*
 #'runtime.q/a
 = a
 3




 On Thu, Feb 21, 2013 at 3:51 PM, AtKaaZ atk...@gmail.com wrote:

 I think the assert is working but either something eats up the thrown
 exception silently which would explain why def isn't reached, OR the
 defcomponent is never called, OR it is called with a different name param
 as you'd have expected. Try putting something before the assert to log if
 that point was ever reached.


 On Thu, Feb 21, 2013 at 3:29 PM, Jim foo.bar jimpil1...@gmail.comwrote:

  oops major typo! the correct is:


 (defmacro defcomponent [name co]
 `(let [c# ~co]
   (assert (component? c#) Not a valid IComponent)
   (def ~name c#)))

 However, this doesn't work! Something weird with the assertion...If I
 comment it out it works as expected, otherwise the var is unbound at the
 end! strange stuffI may end up using 'eval' as I used to...

 Jim



 On 21/02/13 14:20, Jim foo.bar wrote:

 I settled for:

 (defmacro defcomponent [name co]
 `(let [c# ~co]
   (assert (component? c# Not a valid IComponent))
   (def ~name c#)))

 Jim

 On 21/02/13 14:18, AtKaaZ wrote:

  that one doesn't actually work, maybe, not sure why exactly but the
 assert is ignored

 = (def component? number?)
 #'runtime.q/component?

 = (defmacro defcomponent [name co]
 `(assert (component? ~co) Not a valid IComponent)
 `(def ~name ~co))
 #'runtime.q/defcomponent

 = (defcomponent a a)
 #'runtime.q/a


  The `(do ...) one works though,
 = (defmacro a []
  `(println 1)
  `(println 2)
  )
 #'runtime.q/a
 = (a)
 2
 nil

  = (defmacro a []
  `(do
 (println 1)
 (println 2)
 )
  )
 #'runtime.q/a
 = (a)
 1
 2
 nil




 On Thu, Feb 21, 2013 at 3:14 PM, Jim foo.bar jimpil1...@gmail.comwrote:

  I tried this and it works, but I need 2 backticks and I'm essentially
 generating the assert-form when the macro is called...I'd like to generate
 only the def-form at run-time...

 (defmacro defcomponent [name co]
   `(assert (component? ~co) Not a valid IComponent)
   `(def ~name ~co))

 it looks ugly doesn't it?

 Jim




 On 21/02/13 14:11, AtKaaZ wrote:

 or you could place the assert inside the backquote


 On Thu, Feb 21, 2013 at 3:10 PM, Jim foo.bar jimpil1...@gmail.comwrote:

 On 21/02/13 14:07, Jim foo.bar wrote:

 Hi all,

 I''d like to have a macro like the following but preferably without
 the 'eval' inside the assertion form:

 (defmacro defcomponent [name co]
  (assert (component? (eval co)) Not a valid IComponent)
  `(def ~name ~co))

 If I don't use eval, everything works as long as I pass a var
 in...However if I pass in something like (String. jam) it is not being
 evaluated and thus is a list not an object...and it will never satisfy
 IComponent.

 any thoughts?
 thanks in advance :)

 Jim



  I could have phrased this better...One of my arguments has to NOT be
 evaluated (name) but the other needs to be evaluated (co) so I can assert
 whatever I want

Re: Bumi, a project for loading a git repo into a Titan graph database

2013-02-21 Thread Rich Morin

On Feb 21, 2013, at 08:00, Zack Maril wrote:
 Bumi loads a git repo into a Titan graph database[0]. You can then ask 
 questions
 about the history of the project with Faunus[1]. I've successfully loaded the
 Linux kernel onto an AWS instance. I'm working now to start asking good 
 questions
 and see if I can't find out anything neat. Any suggestions about paths of
 investigation to pursue would fall on open ears. ...

Rich Hickey's Codeq project

  http://blog.datomic.com/2012/10/codeq.html

extracts both metadata and code quanta (semantically meaningful code snippets)
from Git repos.  This allows it to answer questions about (say) code churn and 
hot
spots in terms of individual functions, etc.  It also (implicitly) opens the 
door
to other information sources (eg, dynamically harvested metadata).  

I would urge you to consider (a) what can be learned from Codeq and (b) whether
any sort of cooperation and/or interoperability might be possible.

-r

 -- 
http://www.cfcl.com/rdmRich Morin
http://www.cfcl.com/rdm/resume r...@cfcl.com
http://www.cfcl.com/rdm/weblog +1 650-873-7841

Software system design, development, and documentation


-- 
-- 
You received this message because you are subscribed to the Google
Groups Clojure group.
To post to this group, send email to clojure@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+unsubscr...@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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Creating a hash-map with conditional keys

A function could be appropriate, but a macro  not appropriate, since
everything you need here can be done with using macros.
On Feb 21, 2013 7:53 AM, Ryan arekand...@gmail.com wrote:

 Thanks for your input Alex.

 Do you think a macro would be appropriate if I use this more than once in
 my code?

 Ryan

 On Thursday, February 21, 2013 5:41:49 PM UTC+2, Alex Baranosky wrote:

 I'd often just write it like this:

 (defn create-map []
   (merge {:foo a
:bar b
... many more keys}
   (when (some-condition-true)
  {:extra-key value)))


 Alex

 On Thu, Feb 21, 2013 at 7:27 AM, Ryan areka...@gmail.com wrote:

 Thanks Meikel for your reply.

 It wasn't clear on my example, but I wish to use *merge *inside my
 create-map function. Do you think I should bind my hash-map to a let
 variable first and then apply merge, or do you have another proposal? What
 i mean is this:

 (defn create-key-value [value]

  (when (some-condition-true) {:extra-key value))


 (defn create-map []
   (let [my-map {:foo a :bar b}]
 (merge my-map (create-key-value some-value)))


 Is the above clojurish or is there a better way? For example if the
 my-map was a big hash-map, and not with just two pairs, wouldn't it be ugly
 with the above way? or..it's just fine and no better way is possible?

 Ryan

 On Thursday, February 21, 2013 5:02:21 PM UTC+2, Meikel Brandmeyer
 (kotarak) wrote:

 Hi,

 merge works with nil. So (merge (create-map) (create-key-value
 some-value)) should work as you intend with the functions as they are
 defined now.

 Kind regards
 Meikel

  --
 --
 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=enhttp://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_outhttps://groups.google.com/groups/opt_out
 .




  --
 --
 You received this message because you are subscribed to the Google
 Groups Clojure group.
 To post to this group, send email to clojure@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+unsubscr...@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+unsubscr...@googlegroups.com.
 For more options, visit https://groups.google.com/groups/opt_out.




-- 
-- 
You received this message because you are subscribed to the Google
Groups Clojure group.
To post to this group, send email to clojure@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+unsubscr...@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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Creating a hash-map with conditional keys

I got confused a bit with the reason that a macro would not be appropriate 
for this case. Can you please explain again?

Ryan

On Thursday, February 21, 2013 7:05:11 PM UTC+2, Alex Baranosky wrote:

 A function could be appropriate, but a macro  not appropriate, since 
 everything you need here can be done with using macros.
 On Feb 21, 2013 7:53 AM, Ryan areka...@gmail.com javascript: wrote:

 Thanks for your input Alex.

 Do you think a macro would be appropriate if I use this more than once in 
 my code?

 Ryan

 On Thursday, February 21, 2013 5:41:49 PM UTC+2, Alex Baranosky wrote:

 I'd often just write it like this:

 (defn create-map []
   (merge {:foo a
:bar b
... many more keys}
   (when (some-condition-true)
  {:extra-key value)))


 Alex

 On Thu, Feb 21, 2013 at 7:27 AM, Ryan areka...@gmail.com wrote:

 Thanks Meikel for your reply.

 It wasn't clear on my example, but I wish to use *merge *inside my 
 create-map function. Do you think I should bind my hash-map to a let 
 variable first and then apply merge, or do you have another proposal? What 
 i mean is this:

 (defn create-key-value [value] 

  (when (some-condition-true) {:extra-key value)) 


 (defn create-map [] 
   (let [my-map {:foo a :bar b}]
 (merge my-map (create-key-value some-value)))


 Is the above clojurish or is there a better way? For example if the 
 my-map was a big hash-map, and not with just two pairs, wouldn't it be 
 ugly 
 with the above way? or..it's just fine and no better way is possible?

 Ryan 

 On Thursday, February 21, 2013 5:02:21 PM UTC+2, Meikel Brandmeyer 
 (kotarak) wrote:

 Hi,

 merge works with nil. So (merge (create-map) (create-key-value 
 some-value)) should work as you intend with the functions as they are 
 defined now.

 Kind regards
 Meikel

  -- 
 -- 
 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=enhttp://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_outhttps://groups.google.com/groups/opt_out
 .
  
  


  -- 
 -- 
 You received this message because you are subscribed to the Google
 Groups Clojure group.
 To post to this group, send email to clo...@googlegroups.comjavascript:
 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 javascript:
 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 javascript:.
 For more options, visit https://groups.google.com/groups/opt_out.
  
  



-- 
-- 
You received this message because you are subscribed to the Google
Groups Clojure group.
To post to this group, send email to clojure@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+unsubscr...@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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Bumi, a project for loading a git repo into a Titan graph database

2013-02-21 Thread Zack Maril

codeq looks fantastic and I've looked into using it before. The project 
seems to have undergone a flurry of activity last October/November and then 
nothing has really happened with it since then. I haven't seen anybody 
actually do anything impressive with it, so I decided to write Bumi 
instead. If you can point me towards an example of someone doing something 
nontrivial with the project, then I'd happily reconsider starting another 
code analysis project in clojure. codeq looks fantastically powerful from 
the outside, but nobody has done anything yet with it that would actually 
exhibit this perceived power. Which worries me, since if it were so 
powerful, somebody would have easily done something neat with it by now and 
talked about it. The lack of results implies to me that it might not be as 
powerful or useful as people say. 
-Zack

On Thursday, February 21, 2013 8:19:59 PM UTC+4, Rich Morin wrote:

 On Feb 21, 2013, at 08:00, Zack Maril wrote: 
  Bumi loads a git repo into a Titan graph database[0]. You can then ask 
 questions 
  about the history of the project with Faunus[1]. I've successfully 
 loaded the 
  Linux kernel onto an AWS instance. I'm working now to start asking good 
 questions 
  and see if I can't find out anything neat. Any suggestions about paths 
 of 
  investigation to pursue would fall on open ears. ... 

 Rich Hickey's Codeq project 

   http://blog.datomic.com/2012/10/codeq.html 

 extracts both metadata and code quanta (semantically meaningful code 
 snippets) 
 from Git repos.  This allows it to answer questions about (say) code churn 
 and hot 
 spots in terms of individual functions, etc.  It also (implicitly) opens 
 the door 
 to other information sources (eg, dynamically harvested metadata).   

 I would urge you to consider (a) what can be learned from Codeq and (b) 
 whether 
 any sort of cooperation and/or interoperability might be possible. 

 -r 

  -- 
 http://www.cfcl.com/rdmRich Morin 
 http://www.cfcl.com/rdm/resume r...@cfcl.com javascript: 
 http://www.cfcl.com/rdm/weblog +1 650-873-7841 

 Software system design, development, and documentation 




-- 
-- 
You received this message because you are subscribed to the Google
Groups Clojure group.
To post to this group, send email to clojure@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+unsubscr...@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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Creating a hash-map with conditional keys

Macros should be avoided if you don't need them. Otherwise they
drastically reduce code readability. In this case you just have some
predicates and maps that need to be combined conditionally, so nothing
macros do is needed. The real question here is why you would need a macro?
Macros usage is, to me, a question of need, meaning I need to convince
myself that you need it or I wouldn't sacrifice code readability for it.

Things macros are good for:

- delayed code evaluation
- DSL creation
- moving computation to compile time (comes up occasionally)
- other metaprogramming, which I usually only consider worth it if it
reduces duplication enough

Alex

On Thu, Feb 21, 2013 at 9:11 AM, Ryan arekand...@gmail.com wrote:

I got confused a bit with the reason that a macro would not be appropriate
for this case. Can you please explain again?

Ryan

On Thursday, February 21, 2013 7:05:11 PM UTC+2, Alex Baranosky wrote:

A function could be appropriate, but a macro not appropriate, since
everything you need here can be done with using macros.
On Feb 21, 2013 7:53 AM, Ryan areka...@gmail.com wrote:

Thanks for your input Alex.

Do you think a macro would be appropriate if I use this more than once
in my code?

Ryan

On Thursday, February 21, 2013 5:41:49 PM UTC+2, Alex Baranosky wrote:

I'd often just write it like this:

(defn create-map []
(merge {:foo a
:bar b
... many more keys}
(when (some-condition-true)
{:extra-key value)))

Alex

On Thu, Feb 21, 2013 at 7:27 AM, Ryan areka...@gmail.com wrote:

Thanks Meikel for your reply.

It wasn't clear on my example, but I wish to use *merge *inside my
create-map function. Do you think I should bind my hash-map to a let
variable first and then apply merge, or do you have another proposal? What
i mean is this:

(defn create-key-value [value]

(when (some-condition-true) {:extra-key value))

(defn create-map []
(let [my-map {:foo a :bar b}]
(merge my-map (create-key-value some-value)))

Is the above clojurish or is there a better way? For example if the
my-map was a big hash-map, and not with just two pairs, wouldn't it be
ugly
with the above way? or..it's just fine and no better way is possible?

Ryan

On Thursday, February 21, 2013 5:02:21 PM UTC+2, Meikel Brandmeyer
(kotarak) wrote:

Hi,

merge works with nil. So (merge (create-map) (create-key-value
some-value)) should work as you intend with the functions as they are
defined now.

Kind regards
Meikel

--
--
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=enhttp://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/**grou**ps/opt_outhttps://groups.google.com/groups/opt_out
.

--
--
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=enhttp://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_outhttps://groups.google.com/groups/opt_out
.

--
--
You received this message because you are subscribed to the Google
Groups Clojure group.
To post to this group, send email to clojure@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+unsubscr...@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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

--
--
You received this message because you are subscribed to the Google
Groups Clojure group.
To post to this group,

Re: Creating a hash-map with conditional keys

2013-02-21 Thread Jim - FooBar();

I think Alex is trying to say that a macro is almost never appropriate 
when a first-class function would do...therefore, there is no good 
reason for carrying the complexity of macros all over your code, given 
that in your case they do nothing special (like postponed evaluation) 
and can be replaced by functions.


Jim


On 21/02/13 17:11, Ryan wrote:
I got confused a bit with the reason that a macro would not be 
appropriate for this case. Can you please explain again?


Ryan

On Thursday, February 21, 2013 7:05:11 PM UTC+2, Alex Baranosky wrote:

A function could be appropriate, but a macro  not appropriate,
since everything you need here can be done with using macros.

On Feb 21, 2013 7:53 AM, Ryan areka...@gmail.com javascript:
wrote:

Thanks for your input Alex.

Do you think a macro would be appropriate if I use this more
than once in my code?

Ryan

On Thursday, February 21, 2013 5:41:49 PM UTC+2, Alex
Baranosky wrote:

I'd often just write it like this:

(defn create-map []
  (merge {:foo a
   :bar b
   ... many more keys}
  (when (some-condition-true)
 {:extra-key value)))


Alex

On Thu, Feb 21, 2013 at 7:27 AM, Ryan areka...@gmail.com
wrote:

Thanks Meikel for your reply.

It wasn't clear on my example, but I wish to use
*merge *inside my create-map function. Do you think I
should bind my hash-map to a let variable first and
then apply merge, or do you have another proposal?
What i mean is this:

(defn create-key-value [value] 

 (when (some-condition-true) {:extra-key value)) 



(defn create-map []
(let [my-map {:foo a :bar b}]
  (merge my-map (create-key-value some-value)))


Is the above clojurish or is there a better way? For
example if the my-map was a big hash-map, and not with
just two pairs, wouldn't it be ugly with the above
way? or..it's just fine and no better way is possible?

Ryan

On Thursday, February 21, 2013 5:02:21 PM UTC+2,
Meikel Brandmeyer (kotarak) wrote:

Hi,

merge works with nil. So (merge (create-map)
(create-key-value some-value)) should work as
you intend with the functions as they are defined now.

Kind regards
Meikel

-- 
-- 
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
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
https://groups.google.com/groups/opt_out.



-- 
-- 
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
javascript:
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 javascript:
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
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 javascript:.
For more options, visit
https://groups.google.com/groups/opt_out
https://groups.google.com/groups/opt_out.


--
--
You received this message because you are subscribed to the Google
Groups Clojure group.
To post

Re: Creating a hash-map with conditional keys