[petsc-dev] your updates

[Barry Smith]

  Paul,

    PETSc code should never have printf()s or fprintf()s. If there is an error (option passed in wrong etc) then that calls for SETERRQ(). PetscInfo() can be used to print informative messages for tracking what is going on.  NO PRINTFS

     CHKERRCUSP() should only be called on error codes returned from CUSP/CUDA routines, not on PetscErrorCodes returned from other PETSc routines etc.

     }
      else   is wrong.  It needs to always be } else { all the on the same line. See the developers guide http://www.mcs.anl.gov/petsc/developers/developers.pdf

     ALWAYS make sure you pull from petsc-dev before you make changes to your copy because we will likely be putting fixes into various places as users report problems and you don't want to be faced with a big merge after 6 months.

   Barry