Re: [Matlisp-users] Re: Matrix column access

[Raymond T. <ray...@er...>]

>>>>> "Nicolas" == Nicolas Neuss <Nic...@iw...> writes:

    Nicolas> Hello Ray,

Hello!

    >> I would be happy to incorporate any or all of these things into
    >> matlisp, if you are willing to donate them and if they seem
    >> appropriate.

    Nicolas> Yes, I would be willing to donate it.  The question is, if the benefit is
    Nicolas> in a suitable relation to the work to do.  In my eyes, a reasonable work
    Nicolas> program for improving Matlisp would be the following:

Cool.

    Nicolas> 1. One should use the FL.MATLISP matrix structures (automatically
    Nicolas>    generated) for Matlisp.  Printing and read-macro [] should be taken from
    Nicolas>    Matlisp.

What are FL.MATLISP matrix structures?

    Nicolas> 2. One should automate Matlisp's BLAS interface.  Something like (get-blas
    Nicolas>    'daxpy) should make the Fortran daxpy routine available.

I don't follow what you mean by this.  They're always available in
Matlisp.

    Nicolas> 3. Also Matlisp's methods for BLAS and LAPACK generic functions which
    Nicolas>    interface the Fortran routines should be automatically generated
    Nicolas>    whenever possible, maybe following the route I took in Femlisp.  It

Yes, that's possible.  I think there was confusion on what to expose
and how.  Was there supposed to be a very low-level interface to
LAPACK/BLAS, or should the interface be a bit higher-level and more
lisp?  Or what?  I think we ended up with a somewhat incoherent mix,
mostly driven by what users (mostly Tunc) wanted.

    Nicolas>    would be nice if one could also extract documentation.

That's a bit harder because the docs are just comments in the LAPACK
routines themselves.

    Nicolas> 4. Extensions like matrix slices, etc, allowing easy translation of Matlab
    Nicolas>    code should be provided.

I think Simon Alexander has a very fast Lisp matrix slicing package.  Don't
know if it would work with Matlisp or not.

    Nicolas> This program is nontrivial, and at the moment I cannot afford to work on
    Nicolas> it, since I am searching for a job.

Good luck in your job search!

Ray