warn message in log summary

2007-12-06 Thread Matthew Knepley
On Dec 6, 2007 9:00 PM, Barry Smith wrote: > > When we started PETSc 2 I thought of PETSc errors as ALWAYS being > catastrophic: that is the program could NOT continue running. > >Later we started to play with possibly recovering from some errors > and I added the crude PetscException mech

warn message in log summary

2007-12-06 Thread Barry Smith
When we started PETSc 2 I thought of PETSc errors as ALWAYS being catastrophic: that is the program could NOT continue running. Later we started to play with possibly recovering from some errors and I added the crude PetscException mechanism. For example I used it to allow the user in thei

change to Fortran PetscTruth in petsc-dev

2007-12-06 Thread Barry Smith
I have changed the definition of PetscTruth in Fortran in petsc- dev to logical*4. This will require small changes in Fortran code, for example if (flg .eq. PETSC_TRUE) would become if (flg) For backward compatibility you can put a #define PETSC_FORTRAN_PETSCTRUTH_INT 1 into PETSC_ARCH/con