On Thu, Oct 23, 2008 at 5:09 PM, John Peterson <[EMAIL PROTECTED]> wrote:
> We want ShellMatrix to be usable by either Petsc or Epetra, so I don't see
> the reason for creating separate PetscShellMatrix and EpetraShellMatrix
> subclasses...
>
The user's shell matrix _will_ be usable by either Petsc or Epetra...
they're going to call the ShellMatrix interface functions.
The trouble is that you have to put the petsc and epetra specific stuff
_somewhere_. For instance with Petsc... where are you going to call
MatCreateShell()? That's the type of stuff I was intending to be in
Petsc/EpetraShellMatrix. Again, this directly mirrors what happens with
NonlinearSolver...
Derek
-------------------------------------------------------------------------
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