[petsc-dev] meaning of PETSC_USE_EXTERN_CXX?

[Matthew Knepley]

On Tue, Mar 5, 2013 at 7:19 PM, Jed Brown <jedbrown at mcs.anl.gov> wrote:

>
> On Tue, Mar 5, 2013 at 6:03 PM, Matthew Knepley <knepley at gmail.com> wrote:
>
>> Matt, what is this about?
>>>
>>
>> I think this is Satish (blame gets confused by the move).
>>
>
>
> https://bitbucket.org/petsc/petsc-dev/commits/31d7f3bac39971d5406309dcc1cc1df33996fbe9
>

Hmm.


>
>
>> Don't we wrap the entire interface in EXTERN_C
>> so that C++ people who include the header do not mangle PETSc functions?
>>
>
> I was asking about the second block. I don't understand why we would ever
> want the C header to be broken when include from C++.
>

Broken? My interpretation was that this define was turning on extern C for
the interface.

   Matt

-- 
What most experimenters take for granted before they begin their
experiments is infinitely more interesting than any results to which their
experiments lead.
-- Norbert Wiener
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20130305/2b38569b/attachment.html>