[petsc-dev] __func__

[Jed Brown]

Karl Rupp <rupp at iue.tuwien.ac.at> writes:

>>    Will we lose all stack information on Windows?   That is does the Intel Windows compiler do it right? Does the Microsoft compiler (post 2010) do it right?
>> If it is verified that things work ok on Windows then yes it is time to remove them all.
>
> Visual Studio 2012 and older provide __FUNCTION__, but not __func__.
> Visual Studio 2013 and younger additionally support __func__:
> https://msdn.microsoft.com/en-us/library/b0084kay.aspx

Great.

> Maybe some fun with Intel compilers older than 12.0:
> https://software.intel.com/en-us/articles/treating-func-and-function-as-string-literals

__func__ is not supposed to be a string literal and

  -Qoption,cpp,--treat_func_as_string_literal_cpp

is idiotic.  So the issue on that page won't affect us.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 818 bytes
Desc: not available
URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20150617/e131087f/attachment.sig>