On Mon, Jan 7, 2013 at 3:29 PM, Matthew Knepley <knepley at gmail.com> wrote:
> The PetscOptions and PetscInfo functions are examples where we used > _Private to > indicate a lower level interface, rather than one that was truly file > scope. I guess we > need two different specifiers. > Most of these are in matimpl.h and vecimpl.h. They should perhaps be called _Internal since they are shared inside PETSc, but not public. We should also change them from PETSC_EXTERN so that we can set visibility=hidden to prevent users from calling them through shared libraries. ;-) I don't have a problem with non-namespaced functions at file local scope, they just have to be renamed if they are ever referenced from elsewhere. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20130107/cec40fd5/attachment.html>
