Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: David Carlton <carlton@math.stanford.edu>
To: Andrew Cagney <ac131313@redhat.com>
Cc: gdb-patches@sources.redhat.com, ezannoni@redhat.com, jimb@redhat.com
Subject: Re: [commit] remove DEPRECATED_SYMBOL_NAME uses from symtab.c
Date: Thu, 12 Jun 2003 17:05:00 -0000	[thread overview]
Message-ID: <ro1isrb6xaq.fsf@jackfruit.Stanford.EDU> (raw)
In-Reply-To: <3EE8B108.7020306@redhat.com>

On Thu, 12 Jun 2003 12:57:44 -0400, Andrew Cagney <ac131313@redhat.com> said:

> Does this:
>> #define COMPLETION_LIST_ADD_SYMBOL(symbol, sym_text, len, text, word) \
>> -  do { \
>> -    if (SYMBOL_DEMANGLED_NAME (symbol) != NULL) \
>> -      /* Put only the mangled name on the list.  */ \
>> -      /* Advantage:  "b foo<TAB>" completes to "b foo(int, int)" */ \
>> -      /* Disadvantage:  "b foo__i<TAB>" doesn't complete.  */ \
>> completion_list_add_name \
>> -	(SYMBOL_DEMANGLED_NAME (symbol), (sym_text), (len), (text), (word)); \
>> -    else \
>> -      completion_list_add_name \
>> -	(DEPRECATED_SYMBOL_NAME (symbol), (sym_text), (len), (text), (word)); \
>> -  } while (0)
>> +	(SYMBOL_NATURAL_NAME (symbol), (sym_text), (len), (text), (word))

> mean that COMPLETION_LIST_ADD_SYMBOL is also dead?  (I have trouble
> reading unified diffs :-)

No, it's still there, it's just defined as follows now:

#define COMPLETION_LIST_ADD_SYMBOL(symbol, sym_text, len, text, word) \
      completion_list_add_name \
	(SYMBOL_NATURAL_NAME (symbol), (sym_text), (len), (text), (word))

One could argue the wisdom of keeping it around as a separate macro,
but that's a separate issue: all I wanted to do with that patch was
clean up deprecated stuff.

David Carlton
carlton@math.stanford.edu


  parent reply	other threads:[~2003-06-12 17:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-12 15:55 David Carlton
2003-06-12 16:57 ` Andrew Cagney
2003-06-12 17:01   ` Daniel Jacobowitz
2003-06-12 17:05   ` David Carlton [this message]
2003-06-12 17:12     ` Andrew Cagney

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=ro1isrb6xaq.fsf@jackfruit.Stanford.EDU \
    --to=carlton@math.stanford.edu \
    --cc=ac131313@redhat.com \
    --cc=ezannoni@redhat.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=jimb@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