From: Bernardo Innocenti <bernie@develer.com>
To: Alexandre Oliva <aoliva@redhat.com>
Cc: Ian Lance Taylor <ian@wasabisystems.com>,
GCC Patches <gcc-patches@gcc.gnu.org>,
gdb-patches@sources.redhat.com, binutils@sources.redhat.com,
DJ Delorie <dj@redhat.com>
Subject: Re: [top-level] C++-friendly allocators for libiberty
Date: Sun, 27 Jun 2004 05:05:00 -0000 [thread overview]
Message-ID: <40DE55A8.4000905@develer.com> (raw)
In-Reply-To: <orwu1uqigt.fsf@livre.redhat.lsd.ic.unicamp.br>
Alexandre Oliva wrote:
> On Jun 26, 2004, Bernardo Innocenti <bernie@develer.com> wrote:
>
>> #define foo ,
>> xresize(struct foo, f, 10);
>
>>...but how could one possibly abuse this to generate code
>>that actually compiles?
>
> If it's C++, one could overload xrealloc. I tend to prefer to enclose
> all macro arguments in parentheses, even when not strictly necessary,
> than to risk missing one case.
OK, better safe than sorry, I guess.
> And, as Falk pointed out, the full expansion of the macro should be
> enclosed in parentheses as well.
Done already.
--
// Bernardo Innocenti - Develer S.r.l., R&D dept.
\X/ http://www.develer.com/
next prev parent reply other threads:[~2004-06-27 5:05 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-26 0:50 Bernardo Innocenti
2004-06-26 1:05 ` Bernardo Innocenti
2004-06-26 1:14 ` Ian Lance Taylor
2004-06-26 1:27 ` Bernardo Innocenti
2004-06-26 2:19 ` Ian Lance Taylor
2004-06-26 2:39 ` Bernardo Innocenti
2004-06-26 2:46 ` Daniel Jacobowitz
2004-06-26 3:04 ` Bernardo Innocenti
2004-06-26 17:22 ` Andrew Cagney
2004-06-26 17:37 ` Daniel Jacobowitz
2004-06-26 17:51 ` Andrew Cagney
2004-06-27 5:36 ` Bernardo Innocenti
2004-06-28 15:43 ` Andrew Cagney
2004-06-28 18:27 ` Bernardo Innocenti
2004-06-28 18:52 ` Joseph S. Myers
2004-07-01 7:18 ` Bernardo Innocenti
2004-06-26 3:45 ` Alexandre Oliva
2004-06-26 4:18 ` Bernardo Innocenti
2004-06-26 18:31 ` Alexandre Oliva
2004-06-27 5:05 ` Bernardo Innocenti [this message]
2004-06-26 4:56 ` Zack Weinberg
2004-06-26 11:19 ` Falk Hueffner
2004-06-26 16:52 ` Bernardo Innocenti
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=40DE55A8.4000905@develer.com \
--to=bernie@develer.com \
--cc=aoliva@redhat.com \
--cc=binutils@sources.redhat.com \
--cc=dj@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=ian@wasabisystems.com \
/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