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

Barry Smith bsmith at mcs.anl.gov
Mon Jan 7 15:11:04 CST 2013


On Jan 7, 2013, at 3:02 PM, Jed Brown <jedbrown at mcs.anl.gov> wrote:

> On Mon, Jan 7, 2013 at 2:39 PM, Barry Smith <bsmith at mcs.anl.gov> wrote:
>  I think you should namespace the Seg thingy with Petsc and I'd advocate namespacing even all the static functions with PETSc, makes code clearer quicker.
> 
> Yeah, I always namespace things that I export or use from more than one file, but I sometimes skip the namespace for very local things that are easy to rename. My thinking was that it makes it clear that thing is very local (and laziness), but I understand the complaints about the missing namespace.

   I have used NameSpaceOtherStuff_Private() in the past to indicate locality/private only. It would be good to have a single consistent model for indicating.

    Suggestions? 

  Barry





More information about the petsc-dev mailing list