On Mon, Oct 20, 2008 at 12:34 PM, Jed Brown <[EMAIL PROTECTED]> wrote:
> class Matrix {
> public:
> // not_implemented for all matrix operations (mult, multtranspose, etc)
> protected:
> Mat A_petsc;
> Epetra::RowMatrix A_epetra;
> };
I see what you are getting at, but this violates all the encapsulation
we have worked to achieve in the linear solver interfaces up to this
point. I'm not saying that's intrinsically bad, it's just not the
path we've taken. Unless it were absolutely required, I don't think
the amount of work required for redesigning the whole class hierarchy
in this way is warranted.
FWIW I am coming around to the MatrixBase/NumericMatrix class idea,
and I think this is similar to what you have proposed as well.
--
John
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Libmesh-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/libmesh-devel
