public inbox for kawa@sourceware.org
 help / color / mirror / Atom feed
From: Per Bothner <per@bothner.com>
To: Rafik Naccache [TNTeam] <rafik@tnteam.rocks>, kawa@sourceware.org
Subject: Re: What is the Development Environment of Choice for Kawa?
Date: Thu, 18 Feb 2016 18:57:00 -0000	[thread overview]
Message-ID: <56C61423.4070801@bothner.com> (raw)
In-Reply-To: <56C5EED0.8030500@tnteam.rocks>



On 02/18/2016 08:18 AM, Rafik Naccache [TNTeam] wrote:
> Hi,
>
> Coming from Clojure Land, I am experimenting with various scheme implementations, guile, chicken, racket,...
>
> As I am experimenting Kawa, I was surprised to see how this scheme can actually beat Clojure in terms of speed and elegance, and want to use it in a serious hobby project in which I have to interact with a great share of imperative Java, a setup that would make Clojure suffer...
>
> But then, I can't find what tool is commonly used by the community to develop Kawa: is it emacs with comint? is it slime with the little swank glue-code? maybe something else?

Tooling is Kawa's weak spot - though its compile-time warnings and errors
are better than most "dynamic languages" IMO.

I'm pretty old-school, so I mostly use Emacs (mainly just editing), the REPL,
and print statements. (Very rarely I might use jdb to track down an infinite loop.)
OTOH I write more Java (and lately JavaScript) than I write Scheme ...

A related weakness is connected to Kawa's strength: Kawa does a fair amount of
compile-time optimization and inlining.  This causes problems in interactive
development: you load a function or module, and then edit it and reload it.
Other functions that depend on the change code may no longer work.  A partial
work-around is to use the --no-inline command-line option.  I do have plans
to improve the situation, though a combination of extra indirection and
automatic re-compilation of dependencies.

There are various Emacs packages and/or IDE plugins that can be used.
There is this plugin for Eclipse: https://github.com/schemeway/SchemeScript
However, I don't think it's actively maintained, though the git repo has
seen a few semi-recent updates.  I haven't tried it recently - a status report
would be interesting.

There are also various Emacs packages that can be used, though I don't have
much experience with them.

I have been working recently on improving the Kawa repl, both using DomTerm
and using jline2/jline3.  I have some not-quite-working code - and plenty of ideas :-)
-- 
	--Per Bothner
per@bothner.com   http://per.bothner.com/

  reply	other threads:[~2016-02-18 18:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-18 16:18 Rafik
2016-02-18 18:57 ` Per Bothner [this message]
2016-02-18 19:39   ` mikel evins
2016-02-18 19:59   ` Dominique Boucher
2016-02-18 18:53 F. Rafael Leon
     [not found] <3go6arm3yvsi6iuungnfyd1o.1455824305674@email.android.com>
2016-02-18 21:18 ` RE : " Per Bothner
2016-02-18 21:22   ` mikel evins

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=56C61423.4070801@bothner.com \
    --to=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).