apparent bug with binding (or contrib.sql ?) in current master branches

Hello, The following works on the 1.1.0 release of both clojure and clojure.contrib: $ java -server -Djava.net.preferIPv4Stack=true -Dpid=30893 - Djava.awt.headless=true -cp clojure-1.1.0/clojure.jar:clojure- contrib-1.1.0/clojure-contrib.jar clojure.main Clojure 1.1.0 user= (use

Re: apparent bug with binding (or contrib.sql ?) in current master branches

On Thu, Apr 15, 2010 at 6:27 AM, Joost jo...@zeekat.nl wrote: But on the master branches I get: $ java -server -Djava.net.preferIPv4Stack=true  -Dpid=30893 - Djava.awt.headless=true -cp /home/joost/lib/clojure/clojure-1.2.0- master-SNAPSHOT.jar:/home/joost/lib/clojure-contrib/clojure-

Re: apparent bug with binding (or contrib.sql ?) in current master branches

Is there any written rationale for direct binding? It sounds like a poor man's inlining, except we already have perfectly good opt-in inlining. If these screwy semantics are to remain, an absolute minimum courtesy would be for 'binding' to throw an exception at macro expansion time when one tries