From: Eli Zaretskii <eliz@gnu.org>
To: Vladimir Prus <vladimir@codesourcery.com>
Cc: drow@false.org, gdb-patches@sources.redhat.com, nickrob@snap.net.nz
Subject: Re: MI solib notification
Date: Tue, 17 Feb 2009 20:30:00 -0000 [thread overview]
Message-ID: <uy6w4vmdt.fsf@gnu.org> (raw)
In-Reply-To: <200902172244.48437.vladimir@codesourcery.com>
> From: Vladimir Prus <vladimir@codesourcery.com>
> Date: Tue, 17 Feb 2009 22:44:48 +0300
> Cc: drow@false.org,
> gdb-patches@sources.redhat.com,
> nickrob@snap.net.nz
>
> How about the attached, instead?
> [...]
> +@item =library-loaded,...
> +Reports that a new library file was loaded by the program. This
> +notification has 4 fields---@var{id}, @var{target-name},
> +@var{host-name}, and @var{symbols-loaded}. The @var{id} field is an
> +opaque identifier of the library. For remote debugging case,
> +@var{target-name} and @var{host-name} fields give the name of the
> +library file on the target, and on the host respectively. For native
> +debugging, both those fields have the same value. The
> +@var{symbols-loaded} field reports if the debug symbols for this
> +library are loaded.
That's okay, but now I ask again why not do it like I suggested in the
first place, viz.:
@item =library-loaded,@var{info}
Reports that a new library file was loaded by the program. @var{info}
includes 4 fields:
@table @code
@item id="@var{id}"
Opaque identifier of the library.
@item target-name="@var{target-name}"
@itemx host-name="@var{host-name}"
For remote debugging case, @var{target-name} and @var{host-name}
fields give the name of the library file on the target, and on the
host respectively. For native debugging, both those fields have the
same value.
...
etc., you get the idea. What you suggested now is very close to this,
but I think my suggestion makes it easier to read and grasp.
Also, there's one case in your text of only one space after a period
that ends a sentence.
Thanks.
next prev parent reply other threads:[~2009-02-17 20:28 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-30 23:44 Vladimir Prus
[not found] ` <utz7gzcmo.fsf@gnu.org>
2009-02-01 17:53 ` Daniel Jacobowitz
2009-02-01 18:22 ` Eli Zaretskii
2009-02-01 18:29 ` Daniel Jacobowitz
2009-02-17 19:09 ` Vladimir Prus
2009-02-17 19:45 ` Eli Zaretskii
2009-02-17 19:49 ` Vladimir Prus
2009-02-17 20:30 ` Eli Zaretskii [this message]
2009-02-17 21:45 ` Vladimir Prus
2009-02-17 21:59 ` Vladimir Prus
2009-02-18 7:31 ` Eli Zaretskii
2009-02-18 10:19 ` Vladimir Prus
2009-02-18 19:53 ` Eli Zaretskii
2009-02-18 20:04 ` Vladimir Prus
2009-02-18 22:28 ` Eli Zaretskii
2009-02-18 4:24 ` Eli Zaretskii
2009-02-17 21:37 ` Daniel Jacobowitz
2009-02-17 22:10 ` Pedro Alves
2009-02-18 2:01 ` Pedro Alves
2009-02-01 18:04 ` Daniel Jacobowitz
2009-02-12 9:12 ` Vladimir Prus
2009-02-12 13:22 ` Daniel Jacobowitz
2009-02-12 15:02 ` Vladimir Prus
2009-02-12 15:13 ` Daniel Jacobowitz
2009-02-12 17:35 ` Tom Tromey
2009-02-12 18:02 ` Daniel Jacobowitz
2009-02-12 20:11 ` Tom Tromey
2009-02-12 20:17 ` Vladimir Prus
2009-02-12 20:26 ` Daniel Jacobowitz
2009-02-17 19:08 ` Vladimir Prus
2009-02-12 18:06 ` Pedro Alves
2009-02-12 19:45 ` Pedro Alves
2009-02-12 19:56 ` Tom Tromey
2009-02-12 19:58 ` Daniel Jacobowitz
2009-02-13 2:22 ` Joel Brobecker
2009-02-01 18:47 ` Daniel Jacobowitz
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=uy6w4vmdt.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=drow@false.org \
--cc=gdb-patches@sources.redhat.com \
--cc=nickrob@snap.net.nz \
--cc=vladimir@codesourcery.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