On Tue, Apr 5, 2011 at 14:36, Barry Smith <bsmith at mcs.anl.gov> wrote:
> If it is as simple as you say then I am fine with adding support BUT it > will require "yet another flag" I'm not sure about this. What does PETSc need to do at compile time to expose the C++ interface? Isn't all the genuine C++ in headers anyway (e.g. logging interface in petsclog.hh, Exception and Point in petscsys.hh, almost all of Sieve, the few "*.c" files are obviously C++ only and thus should be renamed)? If indeed the C++ stuff (apart from Sieve) resides only in headers, we could unconditionally enable it when __cplusplus (so users could do a standard C build of PETSc and then use the "C++ bits" when calling PETSc from C++). -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20110405/1bf63a9c/attachment.html>
