From mboxrd@z Thu Jan  1 00:00:00 1970
From: "Joseph S. Myers" <jsm28@cam.ac.uk>
To: gcc@gcc.gnu.org
Cc: martin@xemacs.org
Subject: GCC's <assert.h> and C99
Date: Sat, 16 Sep 2000 02:19:00 -0000
Message-id: <Pine.LNX.4.21.0009161015110.31105-100000@kern.srcf.societies.cam.ac.uk>
X-SW-Source: 2000-09/msg00354.html

C99 requires assertion failure messages from <assert.h> to include the
name of the current function as well as the file name and line number.
GCC's <assert.h> doesn't do this.  Would it be appropriate to fix this by
adding a new __eprintf2 function that takes this information and adjusting
assert.h accordingly?  Or, it was suggested by Martin Buchholz
<martin@xemacs.org> that GCC should be using a SysV ABI function __assert
instead of __eprintf, but this function does not allow for inclusion of
the function name, so given C99 it would seem a bad idea to move to
__assert now.  Is there a corresponding replacement for __assert in the
ABI which does support C99?  If so, it would be appropriate to use that.

-- 
Joseph S. Myers
jsm28@cam.ac.uk