Re: Matrix column access

Raymond Toy:
> >>>>> "Nicolas" == Nicolas Neuss <[email protected]> writes:
>     Nicolas> Yes, I did consider a unification.  I have tried to keep classes and
>     Nicolas> methods very close, so that this should even be relatively easy.
> 
>     Nicolas> On the other hand, the libraries have different purposes.  The FL.MATLISP
>     Nicolas> tries to provide only basic operations avoiding all hassle with external
>     Nicolas> libraries, while Matlisp strives to achieve all the functionality (and
>     Nicolas> performance) of LAPACK.
> 
> 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.
> 
> Since I don't use matlisp at all and since Tunc doesn't seem to be
> using matlisp anymore either, what happens in matlisp really, really
> depends on the users now.  I'm willing to add functionality, but the
> users need to describe what they want.

I started using matlisp very recently and the things that were missing
were:

-- why wasn't pinv (pseudoinverse) incorporated? I had to put it in
   myself, and the patches were posted to the list some months ago...

-- not enough efficient data manipulation tools: the macros I posted for
   operating on rows and columns are an example. I really really need
   those to do anything serious.

-- minor stuff, like min/max.

--J.



-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click