Hi Laurent,

Am 29.05.2009 um 14:21 schrieb Laurent PETIT:

I also didn't see whether it was interesting to have the explicit
defn, I thought that an anonymous function could do the trick.

It is often desirable to have the driver function available,
because it can be passed around, apply'd, etc. I terribly miss
binding* as a driver for the binding macro, because I had
the need to do the binding dynamically directly providing
the map of Var-value pairs. But there is no binding* in core,
so I have to reimplement it everytime.

Note, that the naming problem didn't arise in my original
solution, because the name of the driver function was
derived from the final macro name. So two different macros
wouldn't conflict.

Sincerely
Meikel

Attachment: smime.p7s
Description: S/MIME cryptographic signature

Reply via email to