unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Paul Kinnucan <paulk@mathworks.com>
Subject: Re: Elisp as Java Client
Date: 08 Sep 2003 11:34:22 -0400	[thread overview]
Message-ID: <u8yozqoox.fsf@mathworks.com> (raw)
In-Reply-To: vfsmn74qgi.fsf@rpc71.cs.man.ac.uk

Phillip Lord <p.lord@russet.org.uk> writes:

> >>>>> "Siegfried" == Siegfried Heintze <siegfried@heintze.com> writes:
> 
>   Siegfried> Well not everyone was enthralled with the concept as
>   Siegfried> ELisp as COM client.  What about elisp as a java client?
>   Siegfried> Has anyone done that?
> 
>   Siegfried> It would sure be great to use eclisps plugins from emacs!
> 
> This can be done. The JDEE has a significant amount of talk between
> java, and lisp, although its  mostly lisp calling java, rather than
> vice versa. 


The JDEE combines a Lisp interpreter (Emacs) and a Java interpreter
(the BeanShell), each running as a separate process and communicating
with the other via process I/O. The JDEE talks to the Beanshell in
Java and the Beanshell talks back to Emacs in Elisp. More
specifically, the JDEE sends Java expressions to the BeanShell for
evaluation that invoke Java methods developed specifically for use
with the JDEE.  The Java methods pass results back to Emacs by
printing Lisp expressions to standard out. The Lisp expressions
typically invoke Lisp functions that perform JDEE-related tasks. A
listener on the JDEE-side simply passes the Lisp expressions to the
Emacs Lisp interpreter for evaluation. The interface is very simple
and flexible and has been used to create some elaborate features, such
as field and method completion, that combine Java and Lisp code.

Paul

  reply	other threads:[~2003-09-08 15:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-05 17:51 Elisp as Java Client Siegfried Heintze
2003-09-08  8:47 ` Phillip Lord
2003-09-08 15:34   ` Paul Kinnucan [this message]
2003-09-17 14:59     ` Siegfried Heintze
2003-09-18 15:44       ` Paul Kinnucan

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=u8yozqoox.fsf@mathworks.com \
    --to=paulk@mathworks.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).