[petsc-dev] meaning of PETSC_USE_EXTERN_CXX?

Jed Brown jedbrown at mcs.anl.gov
Tue Mar 5 19:19:01 CST 2013

On Tue, Mar 5, 2013 at 6:58 PM, Barry Smith <bsmith at mcs.anl.gov> wrote:

>  I have created a fork https://bitbucket.org/BarryFSmith/petsc-dev-simp this contains all my changes plus Jed's changes with PETSC_INTERN. It
> works on all configurations I tried.
>    I propose:
>        Jed check it out and fix any thing I broke ASAP.

Unfortunately, gitifyhg is slow for these one-shot pulls, mainly because hg
bookmarks and branches are not namespaced. Perhaps we can hack a
namespacing using the (perpetually unstable) Python API to make these fast.

I'm testing it now.

>        We rework this fork to the new model,  C compiler and C++ compiler
> (with C bindings). (No -with-c-support flag or PETSC_USE_EXTERN_CXX flag)

Can we also get rid of --with-c++-support?

>              We will need to coordinate our edits on this, I am available
> to work on it but will not do anything until Jed tells me what to do. So
> Jed tell me what to do and I'll do it.  Better sooner (like now :-) then
> later.

I would start by deleting all occurrences of PETSC_USE_EXTERN_CXX (assume
it is always defined, but use defined(__cplusplus) for some include guards).

Then I would change all PETSC_EXTERN_C and PETSC_INTERN_C statements to

I don't think we can delete include/*.hh until Sieve is gone.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20130305/f97f18ae/attachment.html>

More information about the petsc-dev mailing list