[petsc-dev] extern "C" anachronism

Jed Brown jed at 59A2.org
Sun Nov 7 14:51:16 CST 2010


http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/build_arch-opensolaris-cxx-pkgs-opt_n-gage.log

"vecregall.c", line 43: Warning (Anachronism): Formal argument 4 of type
int(*)(_p_Vec*) in call to VecRegister(const char*, const char*, const
char*, int(*)(_p_Vec*)) is being passed extern "C" int(*)(_p_Vec*).

And lots of warnings like it.  Is it worth using an extern "C" typedef so
that the argument of XXXRegister is labeled extern "C", or is it not worth
it?

Jed
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20101107/e0e6614c/attachment.html>


More information about the petsc-dev mailing list