Re: Sparse matrix problem

[David Bateman]

John W. Eaton wrote:
> On  3-Jan-2007, David Bateman wrote:
>
> | Ok, this was a lot more work than I though it would be, but here is the
> | patch. Basically it allows scalars to be stored in a sparse matrix
> | container and to be treated as if they were scalars. This is necessary
> | as Mathworks chose the path of letting the user store scalars as sparse
> | matrices rather than automatically reconverting these to scalars. In any
> | case the attached patch makes octave matlab compatible for scalars
> | stored as sparse matrices for all operators...
>
> I applied this patch.  It's unfortunate that we have nice type
> conversions that lead to the right behavior (enforced by the type
> system) but we still must have special cases like this.  Should we
> consider eliminating the special scalar types and handle the special
> scalar cases in the Matrix classes instead?
>   
No, I don't think so. This case only arises as Mathworks doesn't
automatically reconvert scalars in a sparse container back to normal
scalars and so the problem is specific to sparse matrices..

D.

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