From: Jeff Shrager
Subject: MATLAB <-> Lisp interaction?
Date: 
Message-ID: <4vkfln$c3h@usenet.srv.cis.pitt.edu>
Has anyone gone through the legwork of using the MatLab Fortran/C
interaction routines to communicate w/lisp (GCL or XLisp,
preferably. the former)?  Specifically, I'd like to use MatLab as the
math engine under lisp (in order to be able to progam in a real and
reasonable language!*)  MatLab provides a means for doing this from
Fortran and C.

Thanks in advance,
  'Jeff

* Sorry; I couldn't help myself! :)  
  [Those who don't love lisp don't know lisp!]

From: Howard R. Stearns
Subject: Re: MATLAB <-> Lisp interaction?
Date: 
Message-ID: <321DDDD9.1CFBAE39@elwoodcorp.com>
Jeff Shrager wrote:
> 
> Has anyone gone through the legwork of using the MatLab Fortran/C
> interaction routines to communicate w/lisp (GCL or XLisp,
> preferably. the former)?  Specifically, I'd like to use MatLab as the
> math engine under lisp (in order to be able to progam in a real and
> reasonable language!*)  MatLab provides a means for doing this from
> Fortran and C.
> 
> Thanks in advance,
>   'Jeff
> 
> * Sorry; I couldn't help myself! :)
>   [Those who don't love lisp don't know lisp!]

Just out of curiosity, does anyone know what is involved in getting
MACSYMA to work with random external Lisp implementations.  I assume
that MACSYMA has some internal implementation of some Maclisp variant,
but I have no idea to what extent it exposes the Lisp internals.
Without getting into the details of cross process communication (RPC,
CORBA, ILU, etc.), I wonder if the Lisp origins of Macsyma inspired its
current maintainers to provide any sort of general callability
utilities.  

I am also aware of the following, all of which, I belive, are Common
Lisp source that can be loaded into random Lisp implementations:

Mockmma is a mock-up of Mathematica -- an algebraic processing system.
See ftp://peoplesparc.cs.Berkeley.edu/pub/mma.README

Lispstat provides statistical tools.
See http://euler.bd.psu.edu/lispstat/

Quail is a quantitative programming environment from the University of
Waterloo.
See http://setosa.uwaterloo.ca/~ftp/Quail/features.html

CLIP and CLASP are instrumentation and statistical analysis packages,
respectively, from U.Mass
See http://eksl-www.cs.umass.edu/research/clip-clasp-overview.html

The math library at CMU has code for various mathematical functions.
See ftp://ftp.cs.cmu.edu/user/ai/lang/lisp/code/math/0.html
From: Rainer Joswig
Subject: Re: MATLAB <-> Lisp interaction?
Date: 
Message-ID: <joswig-2408961156380001@news.lavielle.com>
In article <·················@elwoodcorp.com>, "Howard R. Stearns"
<······@elwoodcorp.com> wrote:

> MACSYMA to work with random external Lisp implementations.  I assume
> that MACSYMA has some internal implementation of some Maclisp variant,

I think there are Common Lisp implementations (Look for Maxima,
At one time I was able to compile Maxima using MCL 2.0).

> Lispstat provides statistical tools.
> See http://euler.bd.psu.edu/lispstat/

There was a CL version of the maths stuff of XLispstat.

The music software "Common Lisp Music" contains a fair amount
of mathematical algorithms.

There are some packages for image processing (with the usual
amount of math involved).


----


We need a source repository on the net.

- Let's take CL-HTTP, a code walker, a classification engine
  and a simple persistent object store.
- Put in the code from the sources we can get our hands on,
  walk the code, classify the bits and pieces, store the stuff
  in the object store and give the world browsing access via
  CL-HTTP.

How does that sound? Then we would have a great tool to reduce
code duplication and help programmers find the interesting stuff.


Rainer Joswig
From: Jeff Shrager
Subject: Re: MATLAB <-> Lisp interaction?
Date: 
Message-ID: <4volpa$nsh@usenet.srv.cis.pitt.edu>
: > Lispstat provides statistical tools.
: > See http://euler.bd.psu.edu/lispstat/

: There was a CL version of the maths stuff of XLispstat.

I'd been using XLisp-Stat, but switched over to gcl and so lost the
stat part, which was good but wasn't MatLab.  Unfortunately, XLisp is
sort of a toy lisp so I opted in favor of a real lisp implementation;
Alas, the choices one must make in life.  My understanding is that
the XLisp folks are making improvements, but the stat part has to
catch up.  I truly can't imagine why they don't simply convert
entirely to gcl.  

Indeed, amidst all this whining for a modernization of lisp, why
haven't we even among ourselves made a choice to commit to one
particular lisp implementation?  It's not like you're going to improve
it a lot by starting over with a new one.  It's embarassing for us to
whine and complain that to rest of the world keeps reinventing lisp by
some other name (of which I do my share!), when we keep reinventing it
by the SAME name!  And we don't even have the excuse of not knowing
what's right to begin with!

'Jeff