Re: goals for 3.1

[David Bateman]

John W. Eaton wrote:
>    1. Objects:
>         -- Merge object-branch
>         -- Implementation of superiorto/inferiorto
>         -- Operator overloading vs. constant folding
>   
I suppose that now that this code is in Octave the use of dispatch
should be discouraged, within the core of Octave at least. Though
dispatch itself is useful so I'd hate to see it go away. The only code
within Octave itself that uses dispatch is within the DLD-FUNCTIONS code
sparse.cc, splu.cc, spchol.cc, spdet.cc, spfind.cc and spqr.cc. That is
entirely the sparse code. However, for matlab compatibility the sparse
type is of the class "double/bool" and there is no indication of its
sparse nature within the class itself, and so the new object code can
dispatch to a sparse type basedon its class.

Therefore, should all of the sparse dispatch code be merged with the
corresponding functions in the same manner as spkron recently was? Or
are we happy to leave the dispatched sparse functions as is?

Regards
David

-- 
David Bateman                                address@hidden
Motorola Labs - Paris                        +33 1 69 35 48 04 (Ph) 
Parc Les Algorithmes, Commune de St Aubin    +33 6 72 01 06 33 (Mob) 
91193 Gif-Sur-Yvette FRANCE                  +33 1 69 35 77 01 (Fax) 

The information contained in this communication has been classified as: 

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