[petsc-users] Calling MatDestroy on MatGetDiagonalBlock

[Matthew Knepley]

How devastating would it be for Deal.II if we renamed them
MatCreateSubMatrix()? ;)

   Matt

On Tue, Jan 5, 2016 at 5:53 PM, Barry Smith <bsmith at mcs.anl.gov> wrote:

>
>   Yeah, looks like MatGetSubMatrix() and MatGetSubMatrices() didn't get
> renamed to the "current" approach.
>
>    Barry
>
> > On Jan 5, 2016, at 5:46 PM, Bhalla, Amneet Pal S <amneetb at live.unc.edu>
> wrote:
> >
> >
> >
> >> On Jan 5, 2016, at 3:32 PM, Barry Smith <bsmith at mcs.anl.gov> wrote:
> >>
> >> So  get -> no destroy
> >>        create -> destroy
> >
> > Is MatGetSubMatrices() exception to this rule? The manual says to call
> the destroy() function after done with it.
> >
> >
> http://www.mcs.anl.gov/petsc/petsc-current/docs/manualpages/Mat/MatGetSubMatrices.html
>
>


-- 
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-users/attachments/20160105/a39d9edc/attachment.html>