Nathan Collier <[email protected]> writes: >> > Since this doesn't provide error tracing, why can't we use the ierr >> argument >> > to make the wrapper do this abort instead? >> > >> > call PetscFunctionWithSeveralArgs(a,b,c,d,PetscErrAbort) >> > >> > Here, PetscErrAbort would be a special value similar to >> PETSC_NULL_OBJECT. >> > If the wrapper sees it, the wrapper aborts instead of returning. >> Thoughts? >> > > Jed, I don't totally follow you here. Are you suggesting that the PETSc > fortran wrapper itself could be made to call the Abort internally such that > user codes do not need to do anything? If that is what you mean, then user > code would have to check codes or configure with --with-errorchecking=0?
The idea is that if all a caller wants is to abort on error, they would pass a special constant instead of 'ierr', in which case the wrapper would abort instead of returning an error code.
pgpIuLsQJZlhp.pgp
Description: PGP signature
