This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug libc/12153] use of keywords in macro definitions can make compilation fail
- From: "vincent+libc at vinc17 dot org" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sources dot redhat dot com
- Date: Fri, 22 Oct 2010 15:14:48 +0000
- Subject: [Bug libc/12153] use of keywords in macro definitions can make compilation fail
- Auto-submitted: auto-generated
- References: <bug-12153-131@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=12153
Vincent LefÃvre <vincent+libc at vinc17 dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|use of keywords in macro |use of keywords in macro
|definitions (e.g. void in |definitions can make
|assert) can make |compilation fail
|compilation fail |
--- Comment #3 from Vincent LefÃvre <vincent+libc at vinc17 dot org> 2010-10-22 15:14:43 UTC ---
(In reply to comment #1)
> I think this is generally considered to be a bug in the C standard. Given
> the explicit definition in the standard of how assert should be defined
> under NDEBUG it seems fairly clear that committee has never explicitly
> intended such usages to work; it's simply been so obviously a bug that
> no-one has felt the need to spend their time explicitly affirming that.
I agree for assert(), though the explicit definition may be seen itself as a
bug in the standard (in the sense: why should void be an exception to the
rule?). But it seems that <math.h> has similar problems, where the standard
doesn't give an explicit definition.
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.