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

[Nicolas N. <Nic...@iw...>]

Raymond Toy <ray...@er...> writes:

>     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?

FL.MATLISP is the name of the corresponding package in Femlisp.  I do
generate the classes for the types automatically:

(defun standard-matrix (type)
  "Defines the programmatic class @class{standard-matrix} for element type
@arg{type} as extensions of the programmatic class @class{store-vector}."
  (assert (subtypep type 'number))
  (fl.amop:find-programmatic-class
   (list 'standard-matrix (store-vector type))
   (intern (format nil "~A" (list 'STANDARD-MATRIX type)) "FL.MATLISP")))

This makes it possible to have also matrices of single-floats, etc.

>     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.

But not every routine as much as I remember.  And for complete generality,
also the single-float versions should be available.  I think that it should
be possible to automate the process of making such a routine available.

>     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.

I think you did that quite well.  At least I like your generic function
interface.  What I don't like is the duplication of code for the different
matrix classes.

> Good luck in your job search!
> Ray

Thank you,

Nicolas.