Re: [ANN] Instaparse 1.4.4

Hi Jeaye, 1. That's indeed a mistaken breakage, I will fix it. Note that specifically the java.net.URL input is what's not properly handled, so if you call (str (io/resource "...")) that will still work as expected. 2. That's also a bug, due to how defparser quotes all of its arguments and tries

[ANN] data.xml 0.2.0-alpha2

data.xml is a Clojure contrib library that parses and emits XML. Github: https://github.com/clojure/data.xml Changelog: https://github.com/clojure/data.xml/blob/master/CHANGES.md Information on updating the dependency is here . 0.2.0-alph

Re: [ANN] data.xml 0.2.0-alpha1

Sorry for the late response, I had to finish 0.2.0-alpha2, in order to present you with the final API for constructing qnames. Please upgrade. ​::can/mqMessageHeader is a purely syntactic shorthand, which gets expanded by the reader to whatever 'can aliases to in the current namespace. Apparently

Re: [ANN] Instaparse 1.4.4

This is great to see; instaparse is crucial for some of my projects and I appreciate the ongoing development. I've noticed two issues with 1.4.4 which I want to run by you: 1. insta/parser has a breaking change, in that it no longer accepts resources directly I can work around this easily by

Re: Why does "clojure.core/run!" end in an exclamation mark?

I'm curious about `clojure.core/run!` too, but my question is whether it is meant to be a `reduce` variant of `clojure.core/doseq` or it has some other purpose. Shantanu On Saturday, 24 December 2016 21:37:11 UTC+5:30, James Reeves wrote: > > My understanding is that the convention used in cloj

Why does "clojure.core/run!" end in an exclamation mark?

My understanding is that the convention used in clojure.core is to put an exclamation mark onto the end of any function unsafe to run in a transaction. Does the reasoning differ for "run!" or is it assumed that the function passed to "run!" will not usually be idempotent? - James -- You receive

Re: Stack Overflow Question

On 24 December 2016 at 11:48, Jiacai Liu wrote: > how to make correct fn args when create fn using macro > http://stackoverflow.com/q/41312963/2163429?sem=2 > For reference, I posted an answer on StackOverflow. - James -- You received this message because you are subscribed to the Google Grou

Re: Stack Overflow Question

your version is obviously wrong, when '~param will try to resolve param, but no luck On Saturday, December 24, 2016 at 10:07:15 PM UTC+8, Jim foo.bar wrote: > > try the following: > > (defmacro defapihandler [handler-name params & body] > `(defn ~handler-name ['~passed-param] > (let [par

Re: Stack Overflow Question

try the following: |(defmacrodefapihandler [handler-name params & body]`(defn~handler-name ['~passed-param](let[param-keys# (vec(map(comp symbol name :key)~params)){:keysparam-keys#}'~passed-param];; some check~@body))) | Sorry for brevity, I'm on my phone... Dimitris On 24/12/16 13:23, Jiac

Re: Stack Overflow Question

I don’t think your answer is correct. From the expaned macro (defn create-user [passed-param__10243__auto__] (let [param-keys__10244__auto__ (vec (map (comp symbol name :key) [{:key

Re: Stack Overflow Question

you need to use `'~passed-param` in your arg-vector, and the same whenever you use it inside the newly defined fn. HTH, Dimitris On 24/12/16 11:48, Jiacai Liu wrote: how to make correct fn args when create fn using macro http://stackoverflow.com/q/41312963/2163429?sem=2 -- You received this

Stack Overflow Question

how to make correct fn args when create fn using macro http://stackoverflow.com/q/41312963/2163429?sem=2 -- 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