On Dec 22, 2011, at 10:20 AM, Jed Brown wrote:
> On Thu, Dec 22, 2011 at 10:18, Barry Smith <bsmith at mcs.anl.gov> wrote:
> In some cases after certain rows/columns have been removed due to active
> constraints certain OTHER rows end up being identically zero. This is some
> hacky code to remove those rows (since they screw up the linear solve). Just
> leave the code.
>
> No, it is *never* executed due to the if (0) statement! In addition to that
> code never being executed, the call to MatFindNonzeroRows() with unused
> return argument is an *unconditional* memory leak.
I understand it is never executed, what I described is why it is there and
how it has been used in the past.
Barry
