[petsc-dev] PETSC_DESIRE_COMPLEX nonsense

Satish Balay balay at mcs.anl.gov
Fri Nov 2 23:08:06 CDT 2012


one reason [perhaps not a strong enough reason] is to avoid having
complex.h exported into user sourcefiles when petsc is not built with
complex [and force users to not using 'I' in their code]

Satish

On Fri, 2 Nov 2012, Barry Smith wrote:

> 
>    Seems unnecessarily convoluted.  Why not just have PETSC_HAVE_COMPLEX defined if either PETSC_HAVE_CXX_COMPLEX  or PETSC_HAVE_C99_COMPLEX  is defined in petscconf.h 
> 
>    Why restrict knowledge of complex to certain files with #define PETSC_DESIRE_COMPLEX at the top?
> 
>     Barry
> 
> 




More information about the petsc-dev mailing list