[petsc-dev] Nonblocking consensus and alternative "freespace" interface

[Karl Rupp]

Hi,


>     So we are proposing utility functions in PETSc NOT for external
>     users are PetscClassFunction_Internal() and for static functions in
>     a file are PetscClassFunction_Static()?
>
>
> I would prefer _Internal and _Private just because I think it sounds better.

Hmm, I prefer _Internal() and _Static() over Matt's preference. _Private 
clashes with a C++ keyword not having any meaning for a function in 
global scope.

Best regards,
Karli