Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Elena Zannoni <ezannoni@redhat.com>
To: David Carlton <carlton@math.stanford.edu>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [patch] some mindless additions of BLOCK_ macros
Date: Wed, 23 Oct 2002 17:18:00 -0000	[thread overview]
Message-ID: <15799.15245.494644.29674@localhost.redhat.com> (raw)
In-Reply-To: <ro165vs4zzf.fsf@jackfruit.Stanford.EDU>

David Carlton writes:
 > I recently noticed that the BLOCK_ macros weren't used everywhere they
 > could be.  I know Andrew doesn't like macros, but given that these
 > ones are used almost everywhere, they might as well be used
 > everywhere.
 > 

These macros are a bit less evil. They are the precursors to accessor
functions. And Andrew likes those....

Elena



      parent reply	other threads:[~2002-10-24  0:18 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-23 14:17 David Carlton
2002-10-23 16:04 ` Andrew Cagney
2002-10-23 16:19   ` David Carlton
2002-10-23 16:59     ` Andrew Cagney
2002-10-23 17:20       ` David Carlton
2002-10-23 16:24   ` Daniel Jacobowitz
2002-10-23 16:50     ` David Carlton
2002-10-23 17:18 ` Elena Zannoni [this message]

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=15799.15245.494644.29674@localhost.redhat.com \
    --to=ezannoni@redhat.com \
    --cc=carlton@math.stanford.edu \
    --cc=gdb-patches@sources.redhat.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