[petsc-dev] petsc release soon

Barry Smith bsmith at mcs.anl.gov
Mon Mar 12 13:41:20 CDT 2012


On Mar 12, 2012, at 1:36 PM, Jed Brown wrote:

> On Mon, Mar 12, 2012 at 13:30, Jed Brown <jedbrown at mcs.anl.gov> wrote:
> A couple maintenance issues that I think should be addressed.
> 
> 1. Namespace EVERYTHING in conf/variables and $PETSC_ARCH/conf/petscvariables. It should be safe to include these files in someone else's makefile without conflicting with their own stuff.
> 
> 2. Rename all C++ files to *.cxx or whatever so that it's possible to build C++ plugins/implementations, with everything else built using a C compiler.
> 
> 3. Move all private headers from include/private/ to include/petsc/ (convention adopted by hundreds of packages) or include/petsc-private/ (like Tk).

  I prefer petsc-private because if one installs in the xxxx/petsc/  you get this stupid looking  xxxx/petsc/include/petsc.   Better xxxx/petsc/include/petsc-private 

   Barry





More information about the petsc-dev mailing list