[petsc-dev] Naming for functions that are safe to call from threads

[Jed Brown]

On Sat, Feb 16, 2013 at 8:10 PM, Barry Smith <bsmith at mcs.anl.gov> wrote:

>
>   size_t and friends  makes me nervous at _t
>

Good point, _t means type in way too many contexts. We have used _T in a
type macro as well (PETSC_UINTPTR_T, MPIU_SIZE_T, ...).

Maybe _K is not so bad after all.


>
> On Feb 16, 2013, at 8:08 PM, Jed Brown <jedbrown at mcs.anl.gov> wrote:
>
> >
> > On Sat, Feb 16, 2013 at 7:55 PM, Barry Smith <bsmith at mcs.anl.gov> wrote:
> >  _k   _t   ?
> >
> > I think I'd prefer _t or _T. The "kernel" mnemonic is more about the
> intent of the code that usually goes in such a function than the semantics
> of that execution mode.
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20130216/d6e434fc/attachment.html>