This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH 3/3] [Ada/doco] Document the new -ada-task-info GDB/MI command.
- From: Eli Zaretskii <eliz at gnu dot org>
- To: Joel Brobecker <brobecker at adacore dot com>
- Cc: gdb-patches at sourceware dot org, brobecker at adacore dot com
- Date: Sat, 17 Sep 2011 09:45:09 +0300
- Subject: Re: [PATCH 3/3] [Ada/doco] Document the new -ada-task-info GDB/MI command.
- References: <1316201377-14830-1-git-send-email-brobecker@adacore.com> <1316201377-14830-4-git-send-email-brobecker@adacore.com>
- Reply-to: Eli Zaretskii <eliz at gnu dot org>
> From: Joel Brobecker <brobecker@adacore.com>
> Cc: Joel Brobecker <brobecker@adacore.com>
> Date: Fri, 16 Sep 2011 12:29:37 -0700
>
> +@item state
> +The current state of the task.
Would it be a good idea to enumerate the possible states here? Or is
that common knowledge for anyone who is an Ada programmer?
> +@smallexample
> +-thread-info
> +^done,tasks=@{nr_rows="3",nr_cols="8",
You are documenting -ada-task-info, so why the example is for a
different command?
> +@item ada-task-info
> +Indicates the presence of the @code{-ada-task-info} command.
I would use "availability of" or "support for", rather than "presence
of". (Yes, I know the other items use the same language you did; I
think they all should be changed.)
Thanks.