From: Eli Zaretskii <eliz@gnu.org>
To: fnf@diveadx.com
Cc: drow@false.org, jimb@red-bean.com, gdb-patches@sourceware.org
Subject: Re: [PATCH] Fix ptype problem printing typedefs defined differently in different compilation units
Date: Fri, 17 Feb 2006 09:15:00 -0000 [thread overview]
Message-ID: <uaccqibxk.fsf@gnu.org> (raw)
In-Reply-To: <200602161916.00761.fnf@diveadx.com> (message from Fred Fish on Thu, 16 Feb 2006 19:16:00 -0500)
> From: Fred Fish <fnf@diveadx.com>
> Date: Thu, 16 Feb 2006 19:16:00 -0500
> Cc: Jim Blandy <jimb@red-bean.com>, gdb-patches@sourceware.org
>
> On Tuesday 14 February 2006 09:10, Daniel Jacobowitz wrote:
> > This patch seems OK to me; but we really ought to fix up the comment
> > directly above this code that you're changing.
>
> I've think it would be best to split work on this issue up into two parts
>
> (1) Make ptype and whatis handle the same arguments. Currently ptype
> will work on typedefs, but whatis does not. This is the change that
> makes them both use whatis_exp and eliminates ptype_eval.
> [...]
> Here is the patch for (1).
> [...]
> --- 180,191 ----
> whatis_exp (exp, -1);
> }
>
> /* TYPENAME is either the name of a type, or an expression. */
>
> static void
> ptype_command (char *typename, int from_tty)
> {
> ! whatis_exp (typename, 1);
> }
Will the manual's description of the differences between these two
commands be still valid after this change?
next prev parent reply other threads:[~2006-02-17 9:15 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-03 20:17 Fred Fish
2006-01-03 23:15 ` Jim Blandy
2006-01-04 2:46 ` Fred Fish
2006-01-04 3:45 ` Jim Blandy
2006-01-04 11:15 ` Fred Fish
2006-01-04 21:04 ` Fred Fish
2006-01-05 0:21 ` Jim Blandy
2006-01-05 0:26 ` Jim Blandy
2006-01-05 0:54 ` Daniel Jacobowitz
2006-01-05 4:47 ` Jim Blandy
2006-01-15 18:48 ` Daniel Jacobowitz
2006-01-16 4:22 ` Jim Blandy
2006-01-23 15:27 ` Fred Fish
2006-01-23 16:12 ` Daniel Jacobowitz
2006-01-23 16:43 ` Fred Fish
2006-01-23 19:17 ` Jim Blandy
2006-01-23 19:35 ` Fred Fish
2006-01-23 20:45 ` Jim Blandy
2006-02-11 0:39 ` Fred Fish
2006-02-11 18:35 ` Daniel Jacobowitz
2006-02-11 19:08 ` Eli Zaretskii
2006-02-11 20:13 ` Daniel Jacobowitz
2006-02-11 20:01 ` Fred Fish
2006-02-11 20:21 ` Daniel Jacobowitz
2006-02-12 18:49 ` Fred Fish
2006-02-14 14:11 ` Daniel Jacobowitz
2006-02-14 18:47 ` Fred Fish
2006-02-17 0:17 ` Fred Fish
2006-02-17 9:15 ` Eli Zaretskii [this message]
2006-02-17 13:36 ` Fred Fish
2006-02-17 20:32 ` Fred Fish
2006-02-18 9:27 ` Eli Zaretskii
2006-02-18 22:19 ` Daniel Jacobowitz
2006-02-20 15:47 ` Fred Fish
2006-02-20 16:23 ` Daniel Jacobowitz
2006-05-17 19:04 ` Fred Fish
2006-02-11 0:39 ` Fred Fish
2006-01-24 15:23 ` [commit] " Fred Fish
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=uaccqibxk.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=drow@false.org \
--cc=fnf@diveadx.com \
--cc=gdb-patches@sourceware.org \
--cc=jimb@red-bean.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