[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: __func__
From: |
Simon Josefsson |
Subject: |
Re: __func__ |
Date: |
Mon, 03 Mar 2008 17:09:52 +0100 |
User-agent: |
Gnus/5.110007 (No Gnus v0.7) Emacs/22.1 (gnu/linux) |
Bruno Haible <address@hidden> writes:
> Simon Josefsson wrote:
>> If there are other pre-C99 compilers that use other ways of printing the
>> function name, I suppose the module could be extended with those.
>
> According to boost/current_function.hpp, it appears that
> - GNU C is not the only compiler to support __PRETTY_FUNCTION__;
> Metrowerks and Intel icc may do the same.
> - Some Intel compilers and some IBM compilers may support __FUNCTION__.
>
> But this info may be out of date. Here's what I verified:
>
> - Intel icc version 9.1 supports __func__, __FUNCTION__,
> __PRETTY_FUNCTION__,
> like GNU C does. And it does not define __STDC_VERSION__.
>
> - HP-UX 11 cc supports __func__, __FUNCTION__. And it does not define
> __STDC_VERSION__ either.
Thanks for testing. As far as I can infer, there is no point in testing
for anything other than __func__ since all platforms that support other
symbols also support __func__?
If we find a platform which doesn't have __func__, but have __FUNCTION__
or something else, we can map the latter to the former. Then we'll know
which platforms are really affected, and can document it better.
/Simon
- Re: __func__, (continued)
Re: __func__, Simon Josefsson, 2008/03/03
Re: __func__,
Simon Josefsson <=