From: Daniel Jacobowitz <drow@false.org>
To: Fred Fish <fnf@specifix.com>
Cc: Jim Blandy <jimb@red-bean.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH] Fix ptype problem printing typedefs defined differently in different compilation units
Date: Sat, 11 Feb 2006 18:35:00 -0000 [thread overview]
Message-ID: <20060211183500.GA25132@nevyn.them.org> (raw)
In-Reply-To: <200602101935.06700.fnf@specifix.com>
On Fri, Feb 10, 2006 at 07:35:06PM -0500, Fred Fish wrote:
> On Monday 23 January 2006 15:45, Jim Blandy wrote:
> > On 1/23/06, Fred Fish <fnf@specifix.com> wrote:
> > > This is why I think the correct and complete solution is to allow the
> > > user to directly specify the context.
> >
> > Sure. That would entail extending the 'type_exp' non-terminal to have
> > a FILENAME COLONCOLON TYPE production. Sounds like the right thing.
>
> The below patch seems to fix ptype and whatis to allow the
> 'file'::typename syntax, without breaking anything else and also
> simplifying ptype_command.
>
> Comments?
Don't you get a warning compiling this? It looks to me like, with
objectprint set, ptype and whatis will now blow up; they call
value_rtti_target_type without initializing val.
Also ptype will now do the RTTI lookup; I'm not sure whether it should
or not. The documentation for whatis and ptype leaves me way
unenlightened about what the difference between them is supposed to
be; perhaps we should eliminate the difference.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-02-11 18:35 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 0:39 ` Fred Fish
2006-02-11 18:35 ` Daniel Jacobowitz [this message]
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
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-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=20060211183500.GA25132@nevyn.them.org \
--to=drow@false.org \
--cc=fnf@specifix.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