[petsc-dev] Removal of PETSC_VIEWER_NATIVE?

Matthew Knepley knepley at gmail.com
Fri Aug 9 09:22:31 CDT 2013

On Fri, Aug 9, 2013 at 9:16 AM, Jed Brown <jedbrown at mcs.anl.gov> wrote:

> Matthew Knepley <knepley at gmail.com> writes:
> > This is something to think about. I believe the original intention here
> was
> > to
> > go along with our philosophy of subtyping. For example, if you call
> >
> >   KSPGMRESSetRestart()
> >
> > on KSPCR, it is just ignored. Likewise ASCII_INFO_DETAIL might just
> > give regular ASCII output if we have no specialization for it. This is
> > more of an open world assumption where we have an acceptable default
> > if we do not know about something.
> What about ASCII_MATLAB or ASCII_VTK?  Printing unstructured text to
> these structured formats is definitely broken.

I don't disagree, but should we go all the way to a closed model to fix
this, or
should we just pick out cases like this and catch them?


What most experimenters take for granted before they begin their
experiments is infinitely more interesting than any results to which their
experiments lead.
-- Norbert Wiener
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20130809/a9f331cc/attachment.html>

More information about the petsc-dev mailing list