From: Eli Zaretskii <eliz@gnu.org>
To: Mary Ma <maryma@mathworks.com>
Cc: gdb@sourceware.org
Subject: Re: How to implement an abbreviated view of a class type
Date: Wed, 24 May 2023 21:27:26 +0300 [thread overview]
Message-ID: <83v8ghmvox.fsf@gnu.org> (raw)
In-Reply-To: <IA1PR05MB92416F68C63ECF741A0C8590DC419@IA1PR05MB9241.namprd05.prod.outlook.com> (message from Mary Ma via Gdb on Wed, 24 May 2023 18:07:06 +0000)
> Date: Wed, 24 May 2023 18:07:06 +0000
> From: Mary Ma via Gdb <gdb@sourceware.org>
>
> However, the challenge I'm facing is that the command line interface displays all the information of a class type at once including inheritance, properties, subclasses. This makes the output overwhelming for developers, especially when encountering cyclic structures.
>
> For instance, it's possible that Type A points to Type B and vice versa, creating a cyclic relationship that makes the view look messy.
>
> I am wondering if there are ways to present an abbreviated view of a type and allow developers to have further control over the amount of detail in the output, depending on what developers want to see.
Did you try using the 'explore' command?
There are also several settings for the 'print' command, all of them
starting with "set print type".
next prev parent reply other threads:[~2023-05-24 18:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-24 18:07 Mary Ma
2023-05-24 18:27 ` Eli Zaretskii [this message]
2023-05-25 13:42 ` Mary Ma
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=83v8ghmvox.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb@sourceware.org \
--cc=maryma@mathworks.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).