Re: Re: Java Interface

Narang,

Narang <[email protected]> writes:

>         http://www.lisp.org/HyperSpec/Body/sec_7-6-6-1-2.html

That does not address any of the problems with automatic conversion that
the SISC manual identifies.

FWIW, SISC is already using a CLOS-like algorithm for method selection.

> As a user I just was SISC to be a more natural extension to Java
> libraries

SISC, first and foremost, aims to be a very good implementation of
Scheme, that, secondly, is running on the JVM. It's design objectives
never included being a natural and convenient mechanism for scripting
Java. We want Java scripting/extension to be possible, have a reasonably
straightforward semantics, and not be too painful, but not at the
expense of the other objectives.

We not want to clutter the SISC core with a lot of code for Java
interop, but we certainly welcome contributions of libraries/modules
that build on the core Java interop framework and make common Java
scripting/extension tasks easier. An example of that is the autos2j code
in contrib. Have you had a look at it? It may address some of the issues
you have been raising.


Matthias.




-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click