Re: Interop nightmare

On Sep 8, 2014, at 9:09 PM, Alan Busby wrote: > On Tue, Sep 9, 2014 at 3:09 AM, Sean Corfield wrote: > > I find that it is quite difficult to use clojure unless one knows Java, > > which I believe to be a barrier to new comers. > > I'm surprised every time I hear this. You can write a lot of

Re: Interop nightmare

On Tue, Sep 9, 2014 at 3:09 AM, Sean Corfield wrote: > > I find that it is quite difficult to use clojure unless one knows Java, > which I believe to be a barrier to new comers. > > I'm surprised every time I hear this. You can write a lot of Clojure > without having to do any interop so you can

Re: Interop nightmare

On Sep 8, 2014, at 4:48 PM, Michael Klishin wrote: > Sounds more like "Just enough Java for Clojure". Which I think would have > too small an audience to be worth the effort. I'd buy it for sure. I bet that some of my students would too. -Lee -- You received this message because you are subs

Re: Interop nightmare

Thanks for all the help! I knew I could count on you guys. I saw that there were a bunch of params in the constructor, but naively hoped there'd be some kind of default values for them so I didn't have to muck around with anything too much. Disappointed once again. I'll look into exactly what e

Re: Interop nightmare

 On 9 September 2014 at 00:33:11, Ivan L (ivan.laza...@gmail.com) wrote: > For an enterprising clojure hacker, this is a good opportunity > to write "Clojure for non-Java Hackers" and put it up on Pragprog. Sounds more like "Just enough Java for Clojure". Which I think would have too small an

Re: Interop nightmare

For an enterprising clojure hacker, this is a good opportunity to write "Clojure for non-Java Hackers" and put it up on Pragprog. On Sunday, September 7, 2014 10:50:31 PM UTC-4, Sam Raker wrote: > > I'm trying to use the Stanford Parser from Clojure, but I don't know > hardly any Java, and this

Re: Interop nightmare

On Monday, September 8, 2014 11:09:50 AM UTC-7, Sean Corfield wrote: > > > I find that it is quite difficult to use clojure unless one knows Java, > which I believe to be a barrier to new comers. > > I'm surprised every time I hear this. You can write a lot of Clojure > without having to do an

Re: Interop nightmare

On Sep 8, 2014, at 10:08 AM, Jacob Goodson wrote: > Hey Sam. I too had great difficulty with clojure interop until I became more > familiar with Java. Yeah, the interop can be painful, especially with the way some Java libraries are "designed" - and you can end up with some pretty ugly Clojure

Re: Interop nightmare

This worked for me: http://viewer.gorilla-repl.org/view.html?source=gist&id=5baef8ac0f42706e4940&filename=parser.clj I had to download the parser distribution from the Stanford NLP site and copy the stanford-parser-3.4.1-models.jar file into the root of my Leiningen project, as I couldn't find

Re: Interop nightmare

Hey Sam. I too had great difficulty with clojure interop until I became more familiar with Java. I find that it is quite difficult to use clojure unless one knows Java, which I believe to be a barrier to new comers. So I suggest that you learn some Java and start trying to hack simple interop

Re: Interop nightmare

Not the answer, but might have some useful clues in ... here's a snippet to make a tagger from the Stanford library: (ns processor.tagger (:require [clojure.data.xml :as xml] [clojure.string :as string]) (:import (edu.stanford.nlp.tagger.maxent TaggerConfig MaxentTagger))) ;; Co

Re: Interop nightmare

On 8 September 2014 at 06:50:38, Sam Raker (sam.ra...@gmail.com) wrote: > I can `(import > edu.stanford.nlp.parser.lexparser.LexicalizedParser)`, > but after that, it's just a nightmare of `no matching ctor`, `no > matching field`, `NoSuchFieldException` and `expected static > field` errors

Re: Interop nightmare

I'm not familiar with the stanford parser, or nlp, but the `no matching ctor error` is easily explained: According to the doc