Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: gdb-patches@sourceware.org
Subject: RFC: remove "info dll" alias to "info sharedlibraries"?
Date: Tue, 30 Dec 2014 07:54:00 -0000	[thread overview]
Message-ID: <20141230075437.GG2123@adacore.com> (raw)

I noticed that windows-nat's _init function makes use of a deprecated
feature:

  deprecated_init_ui_hook = set_windows_aliases;

... where set_windows_aliases just creates an "info dll" alias to
"info sharedlibraries". I think we can rid of the
deprecated_init_ui_hook by simply call add_info_alias in the _init
function, but I'm actually wondering why we wouldn't be able to
just deprecate and then delete the command altogether. We've already
trained the users to use the "sharedlibrary" command, so "info
sharedlibrary" should be easy, and it'll be more consistent with
other targets.

Thoughts? Unnecessary, if we can just call add_info_alias in
the _initialize function, maybe?

-- 
Joel


             reply	other threads:[~2014-12-30  7:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-30  7:54 Joel Brobecker [this message]
2014-12-30 23:22 ` Stan Shebs
2014-12-31  7:31   ` Joel Brobecker
2015-01-05 17:35     ` Pedro Alves
2015-01-05 17:44       ` Joel Brobecker

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=20141230075437.GG2123@adacore.com \
    --to=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    /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