On Apr 6, 2013, at 6:41 PM, Jed Brown <jedbrown at mcs.anl.gov> wrote:
> Barry Smith <bsmith at mcs.anl.gov> writes: > >> petscis.h includes petscsf.h and thus infects almost all petsc >> source code. Should we have a petscissf.h that has the is/sf >> related stuff that is in petscis.h and thus avoid including >> petscsf.h everywhere (like every pc, ksp, and ts file?)? > > Why not split petscsftype.h out of petscsf.h, as per the pattern used > everywhere else? If that would achieve the same object then that sounds fine. So include petscsftypes.h in petscis.h? Barry
