vaclav.hapla at erdw.ethz.ch
Thu May 2 11:13:39 CDT 2019
Is PetscViewerASCIIPushSynchronized / PetscViewerASCIIPopSynchronized really needed?
I just got a feedback it's really confusing.
Why we cannot just switch to the "synchronized mode" with the first call to PetscViewerASCIISynchronizedPrintf, and then hold this mode until PetscViewerFlush, which must be called anyway to get the anticipated output?
What is the motivation for multiple consecutive pushes when this is a boolean state?
I would at least try to improve the documentation anyway. For example, PetscViewerASCIISynchronizedPrintf mentions PetscViewerASCIISynchronizeAllow which no longer exists. I will fix that at once.
More information about the petsc-dev