public inbox for kawa@sourceware.org
 help / color / mirror / Atom feed
From: David Pirotte <david@altosw.be>
To: Per Bothner <per@bothner.com>
Cc: kawa@sourceware.org
Subject: Re: irc
Date: Fri, 18 Sep 2015 23:51:00 -0000	[thread overview]
Message-ID: <20150918205048.1b627982@capac> (raw)
In-Reply-To: <55FC969C.4030902@bothner.com>

[-- Attachment #1: Type: text/plain, Size: 1637 bytes --]


> > so, i want to try kawa, with some help I should, if i'm not mistaken, 'import'
> > any java, any jar, and play the same way, I mean in better ways even, then what
> > i can do using clojure, is this reasonable assumption?
> 
> I've been told that Kawa has better Java integration than Clojure.
> Kawa makes it easy to extend Java classes, use annotations, parameterized types
> (to an extent). If you define-simple-class you get a very straight-forward mapping
> to a Java class. The colon syntax OBJ:PROPERTY first looks for a field PROPERTY in
> OBJ; and then it automatically look for a getPROPERTY method.  Etc etc.

great!

	now i need to read a tutorial on how to ... like i wrote in my last
	imagej/clojure email, as an example of a starting point...

> A big potential advantage is that with Kawa you just need the kawa.jar.  You don't
> need to install and learn a new tool philosopy (i.e. leiningen) - which causes
> extra startup slow-down.  Kawa starts up really fast.

That really totally got me off clojure! exactly, exactly what we don't want to do:
learning another extra 'tool', I totally agree with you and these folks on redit! We
want emacs, scheme, the autotool chain and git [bash, but these days i write my
scripts in scheme as well].


> https://www.reddit.com/r/lisp/comments/2df2rm/should_my_startup_attempt_to_use_abcl_in_a/

> BTW I do recommend building Kawa from Subversion; the "released" jar is a bit old.
> I'd like to make a new official release, but I'm in the middle of various changes.

Any git somewhere? I'm a good git user, no svn experience

Cheers,
David

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]

  reply	other threads:[~2015-09-18 23:51 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-18 21:14 irc Felipe Bueno
2015-09-18 21:23 ` irc Per Bothner
2015-09-18 22:41   ` irc David Pirotte
2015-09-18 22:56     ` irc Per Bothner
2015-09-18 23:51       ` David Pirotte [this message]
2015-09-19  0:15         ` irc Per Bothner
2015-09-19  5:02           ` irc Matthieu Vachon
2015-09-19  7:42             ` irc Per Bothner
  -- strict thread matches above, loose matches on Subject: below --
2015-09-17 19:30 irc David Pirotte
2015-09-17 19:42 ` irc Per Bothner
2015-09-18 19:44   ` irc Jamison Hope
2015-09-19  2:42     ` irc Damien MATTEI

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=20150918205048.1b627982@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).