Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [Ada/NEWS+doco] New Ada maintenance command to ignore descriptive types (DWARF).
Date: Mon, 27 Jan 2014 15:56:00 -0000	[thread overview]
Message-ID: <83iot5a05d.fsf@gnu.org> (raw)
In-Reply-To: <1390797415-6071-1-git-send-email-brobecker@adacore.com>

> From: Joel Brobecker <brobecker@adacore.com>
> Date: Mon, 27 Jan 2014 08:36:55 +0400
> 
> +* New options
> +
> +maint ada set ignore-descriptive-types (on|off)
> +maint ada show ignore-descriptive-types
> +  Control whether the debugger should ignore descriptive types.

I would say "... descriptive types in Ada programs", so that readers
who don't use Ada will not bother looking this up in the manual, even
if they missed the crucial hint in the name of the option.

> +In particular, this convention makes use of @samp{descriptive types},

This should be in @dfn, not @samp, as you are introducing new
terminology.  Also, a @cindex entry for that would be nice.

> +The default is to use descriptives types (@code{off}).
                  ^^^^^^
"not to ignore" is better than "to use" here.

OK with those changes.  However, I wonder if we really should document
this in such a detailed manner, if this is really a temporary measure.
Your call.

Thanks.


  reply	other threads:[~2014-01-27 15:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-27  8:09 Joel Brobecker
2014-01-27 15:56 ` Eli Zaretskii [this message]
2014-01-28  3:09   ` 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=83iot5a05d.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=brobecker@adacore.com \
    --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