On Tue, Aug 14, 2012 at 3:56 PM, Peter Brune <prbrune at gmail.com> wrote:
> Correct; the sheer amount of code using this convention makes it > exceedingly painful to fix. It would be much easier to alter our > internals. I'm *this* close to fugueing on TS especially and removing all > PetscObjects from ctx arguments internal to PETSc. We can pass the TS > around by PetscObjectCompose using the coarsen/restrict hooks. We could also punt with void *PETSC_NULL_FORCE = &knownlocation; I like the dogfooding of having TS pass itself as the context to SNES, but could be convinced to change my mind. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20120814/5843cfbc/attachment.html>