Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Berlin <dberlin@redhat.com>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: Jim Blandy <jimb@cygnus.com>,
	Michael Elizabeth Chastain <chastain@cygnus.com>,
	gdb-patches@sources.redhat.com
Subject: Re: [RFA] Revised C++ ABI abstraction patches
Date: Thu, 15 Mar 2001 15:01:00 -0000	[thread overview]
Message-ID: <m21yryab7p.fsf@dynamic-addr-83-177.resnet.rochester.edu> (raw)
In-Reply-To: <3AB13812.1DDF33AE@cygnus.com>

Andrew Cagney <ac131313@cygnus.com> writes:

> Jim Blandy wrote:
> > 
> > Michael Elizabeth Chastain <chastain@cygnus.com> writes:
> > > Lightly proofread, no obvious errors found.
> > 
> > Great.  That means all the bugs still there are non-obvious, and will
> > take a long time to find.  Just make my day, will you.  (Thanks.)
> > 
> > > I would prefer constructor_prefix_p et al to be real functions rather
> > > than macros.  When I single-step code in gdb, it's a lot easier to follow
> > > real functions than macros.
> > 
> > I agree completely.  But it is not the standard practice (see target.h
> > and elsewhere) and others don't seem to mind.  So I reined in my prima
> > donna urges and left them as macros.
> 
> Standard pratice is to use functions.  Per the thread on the
> xfer_memory() change - target.h will be fixed :-)

Can I make them static inline functions, and keep them in the header,
like the linux kernel does instead of macros?

Or should i just move them to functions in cp-abi.c?

--Dan


  reply	other threads:[~2001-03-15 15:01 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-15 10:50 Michael Elizabeth Chastain
2001-03-15 11:04 ` Jim Blandy
2001-03-15 11:32   ` Michael Snyder
2001-03-15 11:35   ` J.T. Conklin
2001-03-15 12:36     ` Jim Blandy
2001-03-15 15:21       ` Stan Shebs
2001-03-15 17:54         ` Jim Blandy
2001-03-15 20:11           ` Andrew Cagney
2001-03-15 13:46   ` Andrew Cagney
2001-03-15 15:01     ` Daniel Berlin [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-03-15  1:50 Jim Blandy
2001-03-15  3:15 ` Eli Zaretskii
2001-03-15  6:21   ` Fernando Nasser
2001-03-15  6:46     ` Daniel Berlin
2001-03-15 10:40   ` Jim Blandy
2001-03-15 13:38     ` Andrew Cagney
2001-03-15 14:05       ` Jim Blandy
2001-03-16 23:28     ` Eli Zaretskii
2001-03-19  9:38       ` Jim Blandy
2001-03-19 11:58         ` Eli Zaretskii
2001-03-15 14:57 ` Andrew Cagney
2001-03-15 17:57   ` Jim Blandy
2001-03-15 18:10     ` Andrew Cagney
2001-03-15 19:12     ` Daniel Berlin
2001-03-15 19:56       ` Jim Blandy
2001-03-15 18:58   ` Daniel Berlin

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=m21yryab7p.fsf@dynamic-addr-83-177.resnet.rochester.edu \
    --to=dberlin@redhat.com \
    --cc=ac131313@cygnus.com \
    --cc=chastain@cygnus.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=jimb@cygnus.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