public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Tom Tromey <tromey@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Expand dynamic type documentation
Date: Sat, 25 Apr 2020 08:59:45 +0300	[thread overview]
Message-ID: <831roc9kby.fsf@gnu.org> (raw)
In-Reply-To: <20200424203911.26599-1-tromey@adacore.com> (message from Tom Tromey on Fri, 24 Apr 2020 14:39:11 -0600)

> From: Tom Tromey <tromey@adacore.com>
> Date: Fri, 24 Apr 2020 14:39:11 -0600
> Cc: Tom Tromey <tromey@adacore.com>
> 
> This expands the Python dynamic type documentation, as suggested by
> Christian.
> 
> gdb/doc/ChangeLog
> 2020-04-24  Tom Tromey  <tromey@adacore.com>
> 
> 	* python.texi (Types In Python): Mention missing fields.  Add
> 	dynamic type example.

Fine with me, with one minor comment:

> +Here, at least conceptually (whether your compiler actually does this
> +is a separate issue), examining @code{gdb.lookup_symbol("array", ...).type}

This long @code{..} expression is likely to be split between lines; to
prevent that, I suggest to wrap it in @w{..}.

Thanks.

  reply	other threads:[~2020-04-25  5:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-24 20:39 Tom Tromey
2020-04-25  5:59 ` Eli Zaretskii [this message]
2020-04-27 14:28   ` Tom Tromey

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=831roc9kby.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=tromey@adacore.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).