__func__ is what you should use. We take care of having it defined in
_all_ cases. If the compiler doesn't support it we define it manually
(to __FUNCTION__ or to __FILE__ in the worst case), so it is always
available (even if it doesn't contain what one might expect such in
the case of __FILE__).
george.
On Sep 9, 2009, at 14:16 , Lenny Verkhovsky wrote:
Hi All,
does C99 complient compiler is something unusual
or is there a policy among OMPI developers/users that prevent me f
rom using __func__ instead of hardcoded strings in the code ?
Thanks.
Lenny.
On Wed, Sep 9, 2009 at 1:48 PM, Nysal Jan <jny...@gmail.com> wrote:
__FUNCTION__ is not portable.
__func__ is but it needs a C99 compliant compiler.
--Nysal
On Tue, Sep 8, 2009 at 9:06 PM, Lenny Verkhovsky <lenny.verkhov...@gmail.com
> wrote:
fixed in r21952
thanks.
On Tue, Sep 8, 2009 at 5:08 PM, Arthur Huillet <arthur.huil...@bull.net
> wrote:
Lenny Verkhovsky wrote:
Why not using __FUNCTION__ in all our error messages ???
Sounds good, this way the function names are always correct.
--
Greetings, A. Huillet
_______________________________________________
devel mailing list
de...@open-mpi.org
http://www.open-mpi.org/mailman/listinfo.cgi/devel
_______________________________________________
devel mailing list
de...@open-mpi.org
http://www.open-mpi.org/mailman/listinfo.cgi/devel
_______________________________________________
devel mailing list
de...@open-mpi.org
http://www.open-mpi.org/mailman/listinfo.cgi/devel
_______________________________________________
devel mailing list
de...@open-mpi.org
http://www.open-mpi.org/mailman/listinfo.cgi/devel
