Re: [OctDev] Release details

[David B. <Dav...@mo...>]

According to Stefan van der Walt <st...@su...> (on 09/08/04):
> On Wed, Sep 08, 2004 at 01:30:37AM -0400, Paul Kienzle wrote:
> > Hi all,
> > 
> > I posted RELEASE-NOTES.  Check that I've got everything.
> > 
> > Quite the effort for the last couple of months!  Lots of work on
> > comm and fixed as usual.  Some long standing issues addressed
> > in sparse (thanks Andy and David!).  Many extensions to the image
> > processing toolbox.  And of course the usual maintenance
> > (thanks everybody!).
> 
> Somewhat related: what is the current status of the sparse toolbox?
> Will the sparse types eventually go into liboctave?  For now, can one
> use it in oct files?

John has stated on these lists that he doesn't like the use of malloc
in the sparse toolbox and wouldn't accept it as is due to that. He
also pointed out that UMFPACK has better performance than SuperLU and
would prefer that a sparse type in liboctave was based on that.

That said there is no limitation on you using the sparse type within
oct-files, except on the cygwin platform. On cygwin the symbols are
resolved at compile time and so the oct-file would need to be linked
as a shareable library to your own oct-file. I did something like this
with the examples in the fixed point type. See the  files in
main/fixed/examples on how to go about using your types in oct-files..

D.

-- 
David Bateman                                Dav...@mo...
Motorola CRM                                 +33 1 69 35 48 04 (Ph) 
Parc Les Algorithmes, Commune de St Aubin    +33 1 69 35 77 01 (Fax) 
91193 Gif-Sur-Yvette FRANCE

The information contained in this communication has been classified as: 

[x] General Business Information 
[ ] Motorola Internal Use Only 
[ ] Motorola Confidential Proprietary