public inbox for kawa@sourceware.org
 help / color / mirror / Atom feed
From: Helmut Eller <eller.helmut@gmail.com>
To: kawa@sourceware.org
Subject: Re: Environment Introspection
Date: Wed, 20 Sep 2017 07:05:00 -0000	[thread overview]
Message-ID: <m2bmm56eat.fsf@caladan> (raw)
In-Reply-To: <87efr4a7ft.fsf@nexoid.at>

On Mon, Sep 18 2017, Peter wrote:

> I want actual debugging,

When I tried to implement debugging for SLIME, I found Kawa quite
frustrating and eventually gave up for the following reasons:

Debugging, the way SLIME does it, is difficult/impossible because Kawa
uses JVM exceptions for most error handling.  While Kawa has now
`with-exception-handler', few people use it and certainly no Java
libraries use it.

The Kawa code base also has the idiom try {...} catch (Throwable x) in a
number of places, with defeats tricks based on
com.sun.jdi.request.ExceptionRequest.notifyUncaught.

Another problem with Kawa are the unstable/non-existing/constantly
changing APIs to Kawa internals.

I would suggest that you work as closely as you can with Per, so that he
is aware of the issues and doesn't (unintentionally) break your work.
For that reason, it makes a lot of sense to use LSP.  LSP may not have a
"standard" API for debugging, but I think it's fairly easy to add
extensions to LSP for whatever you like.  I would also expect that
writing an Emacs front-end for LSP is easy/fun in comparison to digging
around in Kawa internals.  So let Per do the hard work on the Kawa side
to make a good LSP server and spend your time in on the Emacs side :-).

Helmut

      parent reply	other threads:[~2017-09-20  7:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-17 20:57 Peter
2017-09-17 23:17 ` Per Bothner
2017-09-18  5:44   ` Peter
2017-09-18  6:15     ` Per Bothner
2017-09-20  7:05     ` Helmut Eller [this message]

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=m2bmm56eat.fsf@caladan \
    --to=eller.helmut@gmail.com \
    --cc=kawa@sourceware.org \
    /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).