I’m definitely willing to submit it as a pull request.
Also, while I’m at it, I’m going to write a “duplicate” function for transpose and hermitian_transpose. Just because this seems 1) easy ( MatHermitianTranspose can return a new copy, as well as MatTranspose), and 2) necessary to use these for EPS. Also, is “transpose” a good enough MatType? Or does a new one need to be written? -Andrew On Mon, Feb 23, 2015 at 3:12 PM, Jed Brown <[email protected]> wrote: > Barry Smith <[email protected]> writes: >> The directory include/petsc-private/matimp.h is always provided >> with a PETSc installation so though _p_Mat is "private" to PETSc >> you can extend PETSc "out side of the library proper". > What you don't get when accessing the private headers is a guarantee of > backward compatibility (even across subminor releases) or documentation > of changes in the release notes. If people are using private headers > frequently, we should strive to make a public interface to fulfill their > needs.
