Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <cagney@gnu.org>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [rfa:symtab] deprecate inside_entry_func
Date: Sat, 22 Nov 2003 00:37:00 -0000	[thread overview]
Message-ID: <3FBEAFCB.90601@gnu.org> (raw)
In-Reply-To: <20031121210412.GA2627@nevyn.them.org>


>> That's not what I'm asking.
>> 
>> With the call to inside_entry_func removed, from get_prev_frame, can you 
>> point me at any remainng _legitimate) uses of that function?
> 
> 
> The other call to it in legacy_frame_chain_valid, which wants to know
> the same thing?  I imagine the third caller, in frv-tdep.c, is bogus
> and could be removed somehow.  But if it's going to be left there then
> it seems reasonable to update it also.

I see Kevin's finally removed that bogus call.

> Conceptually the patch you just posted sees to be:
>  - Change the implementation of inside_entry_func
>  - Inline the new inside_entry_func into the one caller you're fond of
>  - Add a deprecated copy of the old implementation for the other
>    callers
> 
>>From the man who is always telling us how unimportant performance is
> compared to clarity, I don't see the point.  Also, this leaves an old
> implementation and a new implementation around for no visible reason.

"Indirection can be helpful, but needless redirection is irritating."

Note that the implementation of the two mechanisms is very different. 
Better to leave old code using the old mechanism, and new code using the 
new mechanism.

Andrew



  parent reply	other threads:[~2003-11-22  0:37 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-01  0:07 Andrew Cagney
2003-11-01  0:37 ` Kevin Buettner
2003-11-01  0:46   ` Andrew Cagney
2003-11-01  0:55     ` Kevin Buettner
2003-11-01  2:27       ` Andrew Cagney
2003-11-07 17:31         ` Kevin Buettner
2003-11-07 21:25           ` Andrew Cagney
2003-11-01  0:42 ` Daniel Jacobowitz
2003-11-01  2:37   ` Andrew Cagney
2003-11-09  0:13     ` Daniel Jacobowitz
2003-11-09  2:40       ` Andrew Cagney
2003-11-09  3:50         ` Daniel Jacobowitz
2003-11-21 19:53 ` Andrew Cagney
2003-11-21 19:59   ` Daniel Jacobowitz
2003-11-21 20:11     ` Kevin Buettner
2003-11-21 20:46     ` Andrew Cagney
2003-11-21 20:48       ` Daniel Jacobowitz
2003-11-21 20:55         ` Andrew Cagney
2003-11-21 21:04           ` Daniel Jacobowitz
2003-11-21 21:24             ` Kevin Buettner
2003-11-21 21:54               ` Daniel Jacobowitz
2003-11-21 22:40                 ` Kevin Buettner
2003-11-22  0:37             ` Andrew Cagney [this message]
2003-11-22  0:41               ` Daniel Jacobowitz
2003-11-21 20:07   ` David Carlton

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=3FBEAFCB.90601@gnu.org \
    --to=cagney@gnu.org \
    --cc=drow@mvista.com \
    --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