public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Stan Shebs <stanshebs@earthlink.net>
To: gdb-patches@sourceware.org
Subject: Re: RFC: remove "info dll" alias to "info sharedlibraries"?
Date: Tue, 30 Dec 2014 23:22:00 -0000	[thread overview]
Message-ID: <54A333AE.1030904@earthlink.net> (raw)
In-Reply-To: <20141230075437.GG2123@adacore.com>

On 12/29/14 11:54 PM, Joel Brobecker wrote:
> 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.

What's the basis for believing that "we've already trained the users"?

With a little poking around the net, I did notice a couple examples
where people were reporting "info dll" results.  But in practice I
suspect that most GDB-using Windows developers are working on multiple
platforms, and they're likely to prefer commands that work everywhere.

On the other hand, "info dll" has been documented for a long time,
and is only one line of extra code - seems like more work to remove
than to leave it alone.

I do think we can dump the hook and just use add_info_alias.  I don't
remember exactly why the hook seemed necessary in the first place, but
the timing suggests I added it for gdbtk or MPW (or both. :-) ).

Stan
stan@codesourcery.com



  reply	other threads:[~2014-12-30 23:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-30  7:54 Joel Brobecker
2014-12-30 23:22 ` Stan Shebs [this message]
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=54A333AE.1030904@earthlink.net \
    --to=stanshebs@earthlink.net \
    --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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).