From: David Pirotte <david@altosw.be>
To: Per Bothner <per@bothner.com>
Cc: kawa@sourceware.org
Subject: Re: imagej - a clojure example
Date: Thu, 24 Sep 2015 23:52:00 -0000 [thread overview]
Message-ID: <20150924205225.7085abdb@capac> (raw)
In-Reply-To: <560464CA.8010008@bothner.com>
[-- Attachment #1: Type: text/plain, Size: 1347 bytes --]
> > (import (ij IJ)) [ if that is correct, I don't know
> > [ if not please correct me
> You need set the classpath before you start up the Java VM - typically
> on the java command line or a CLASSPATH environment variable.
> For example:
> $ CLASSPATH=.:ij.jar kawa
Thanks, someone kindly answered on #kawa. I will mail the example I got so other
may benefit: I did not know a module was auto define based on the name of the
file... and other things jhope explained me on #irc
> > Also, How do I introspect a module? Like once yu tll me how to make these
> > ij-1.49v.jar, mpicbg_-1.0.1.jar, .. known to java, how can I list the public
> > interface of these modules, its classes, methods ...
> Introspection is a complex feature. Kawa doesn't really have an introspection
> API - you can use the Java reflection API or the model API, but these are
> nontrivial; certainly more than a quick reply here. What is your specific
> use-case?
Everything I can do when using clos I guess.
> If you're just trying the learn what's available in a libray, the usual
> method is to look at the javadoc-generated API documentation. For example
> for imagej look here:
Sure, but how do you debug?
Maybe the second jar must be in a specific subdirectory, if that so, how
would I know?
Cheers,
David
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2015-09-24 23:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-18 23:38 David Pirotte
2015-09-24 18:31 ` David Pirotte
2015-09-24 21:02 ` Per Bothner
2015-09-24 23:52 ` David Pirotte [this message]
2015-09-25 1:24 ` David Pirotte
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150924205225.7085abdb@capac \
--to=david@altosw.be \
--cc=kawa@sourceware.org \
--cc=per@bothner.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).