Re: Re: Matrix column access

Jan Rychter <[email protected]> writes:

> Thanks, this is indeed much, much better. Have you considered
> contributing some of your code back to matlisp? I looked at it, and
> there is a lot of nice functionality in your fl.matlisp package (apart
> from minject and mextract I also liked the BLAS-based vector
> operations).

Yes, I did consider a unification.  I have tried to keep classes and
methods very close, so that this should even be relatively easy.

On the other hand, the libraries have different purposes.  The FL.MATLISP
tries to provide only basic operations avoiding all hassle with external
libraries, while Matlisp strives to achieve all the functionality (and
performance) of LAPACK.

> I think this code could be very useful to many people. But it seems it is
> dependent on some other utitilies, and I'd prefer not to pull in the
> entire Femlisp code...

The dependencies are relatively small.  I have once asked here, if there
was interest for a standalone version of FL.MATLISP, but there seemed to be
no real need.  Therefore, this will have to wait until someone needs it
more urgently.  This standalone would then be a natural candidate to
combine with Matlisp.

> As it is, I'll probably reinvent the wheel and write my own functions
> using DCOPY, as you suggested.

I'm quite sure this is the choice fitting the Matlisp way best.  If you
indeed want to make it into a generic function, it would be nice if you
could use my MEXTRACT/MINJECT syntax.  Probably, the Matlisp authors would
also welcome such a contribution.

Nicolas.


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