public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "joseph at codesourcery dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug libc/18604] assert macro-expands its argument
Date: Mon, 29 Jun 2015 14:49:00 -0000	[thread overview]
Message-ID: <bug-18604-131-fTwenw1oiE@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-18604-131@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=18604

--- Comment #3 from joseph at codesourcery dot com <joseph at codesourcery dot com> ---
For early history try git://repo.or.cz/glibc/history (a conversion without 
the heuristics to combine commits to different files from the same 
changeset that were committed with per-file log messages that caused 
problems for some of the earlier history).  The initial version of 
assert.h there from 1991 has (commit 
c2547ce6a46f905a7f876f3e2c35e6e9e9b36527):

+/* IGNORE($    */
+#ifdef __STDC__
+/* $) IFANSI($ */
+#define        __assert_quotearg(s)    #s
+/* $) IGNORE($ */
+#else  /* Not ANSI C.  */
+/* $) IFTRAD($ */
+#define        __assert_quotearg(s)    "s"
+/* $) IGNORE($ */
+#endif /* ANSI C.  */
+/* $)  */

which suggests that pre-ISO C may have been a reason for how this was done 
(although pre-ISO C is no longer a concern now and I agree it would make 
sense to stop macro-expanding here).

-- 
You are receiving this mail because:
You are on the CC list for the bug.


  parent reply	other threads:[~2015-06-29 14:49 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-26  7:35 [Bug libc/18604] New: " dak at gnu dot org
2015-06-28 10:09 ` [Bug libc/18604] " dak at gnu dot org
2015-06-28 11:56 ` schwab@linux-m68k.org
2015-06-29 14:49 ` joseph at codesourcery dot com [this message]
2015-07-03 12:44 ` dak at gnu dot org
2015-07-09  9:25 ` dak at gnu dot org
2015-07-09 21:31 ` msebor at redhat dot com
2015-07-22 20:24 ` joseph at codesourcery dot com

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-18604-131-fTwenw1oiE@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).