[petsc-users] __FUNCT__ does not agree with __FUNCTION__

[Jed Brown]

Satish Balay <balay at mcs.anl.gov> writes:

> One can skip __FUNCT__ alltogether in user sourcefiles [assuming you
> have a c99 compiler] - as  __func__ would automatically be used
> by the petsc macros [in includes]

You can literally skip it everywhere, C99 or not, and PETSc will not
issue these warnings.  If __func__ is not available, traces will say
"User defined function".
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 818 bytes
Desc: not available
URL: <http://lists.mcs.anl.gov/pipermail/petsc-users/attachments/20140708/d0e882ff/attachment.pgp>