Re: Inside Clojure Journal

2019-03-02 Thread Colin Fleming
I for one would appreciate it if you fixed it rather than removing it :-) On Wed, 30 Jan 2019 at 20:07, Alex Miller wrote: > That's never actually worked. I keep meaning to remove it. :) > > On Wednesday, January 30, 2019 at 1:41:16 PM UTC-6, puzzler wrote: >> >> +1. >> >> I can't seem to subscr

Exploring the (tap>) functions

2019-03-02 Thread Glen Mailer
Hello All I was wondering if there is an annoucement or a rationale doc coming for (tap>) and it's related functions? The current docstrings do a good job of telling you what they do and how to use them, but the docs on the homepage seem quite

Re: Clojure 1.10 "Illegal Reflective Access Operation"

2019-03-02 Thread Alan Thompson
I was deceived by the error message. Since I had only changed the Clojure version 1.9 => 1.10, and since the warning mentioned only Clojure code: WARNING: Illegal reflective access by clojure.lang.InjectedInvoker/0x000800231c40 (file:/home/alan/.m2/repository/org/clojure/clojure/1.10.0/cloj

Re: Clojure 1.10 "Illegal Reflective Access Operation"

2019-03-02 Thread Matching Socks
Does this need adjusting in clojure.xml too? The code looks pretty similar: (defn startparse-sax [s ch] (.. SAXParserFactory (newInstance) (newSAXParser) (parse s ch))) The reflection on "parse" is convenient. There are multiple SaxParser.parse methods with unique capabilities. The String met

Re: Exploring the (tap>) functions

2019-03-02 Thread Alex Miller
On Saturday, March 2, 2019 at 1:23:21 PM UTC-6, Glen Mailer wrote: > > Hello All > > I was wondering if there is an annoucement or a rationale doc coming for > (tap>) and it's related functions? The current docstrings do a good job of > telling you what they do and how to use them, but the docs