Ok, makes sense. Thanks On 08/16/2013 11:31 AM, Jed Brown wrote: > John Peterson <[email protected]> writes: >> I think --with-clanguage=cxx causes the complex type in PETSc to be >> std::complex<double>, while without it, the complex type is something else >> C-based (not sure exactly what that's called). > C99 complex. Since the types are binary-equivalent, it would be > possible to make the type masquerade as C99 complex when included from C > code and as std::complex when include from C++ code. Of course this > doesn't work if the user has (non-portable) C++ code that manipulates > C99 complex types.
------------------------------------------------------------------------------ Get 100% visibility into Java/.NET code with AppDynamics Lite! It's a free troubleshooting tool designed for production. Get down to code-level detail for bottlenecks, with <2% overhead. Download for free and get started troubleshooting in minutes. http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk _______________________________________________ Libmesh-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-users
