I wrote some functions to streamline reflection here.
http://groups.google.com/group/clojure/browse_thread/thread/ea23cd11b7bd8999/f32795d9a79eeeb9?lnk=gst&q=accessing+private#f32795d9a79eeeb9
--~--~-~--~~~---~--~~
You received this message because you are subscribe
Thanks for the links, Stuart, although I managed to figure out what I
was doing wrong: I didn't realize that the Java vararg type Object...
mapped to a sequence in Clojure, so I wasn't properly calling 'invoke'
in java.lang.reflect.Method.
Again, thanks for the links. I'm sure they'll be helpful
Hi Geoff,
You should have no trouble using setAccessible. There are several
demos of this in the source code for the book [1] that use
setAccessible to check private fields in a unit test. (See lancet/test/
step-2-complete.clj [2], for instance).
Hope this helps,
Stu
[1] http://github.com
As far as I know, there is no limit.
On Apr 2, 11:22 am, Geoff Wozniak wrote:
> What are the limitations of Clojure and Java interoperability? Are
> they clearly stated somewhere?
>
> I have been experimenting with using Clojure to test some existing
> Java code (being able to do so makes a conv
What are the limitations of Clojure and Java interoperability? Are
they clearly stated somewhere?
I have been experimenting with using Clojure to test some existing
Java code (being able to do so makes a convincing argument to use it
where I work) and I've noticed that there doesn't seem to be an
