From: "Eli Zaretskii" <eliz@gnu.org>
To: Bob Rossi <bob@brasko.net>
Cc: gdb-patches@sources.redhat.com
Subject: Re: MI handshaking
Date: Fri, 05 Nov 2004 17:50:00 -0000 [thread overview]
Message-ID: <01c4c35f$Blat.v2.2.2$3c749800@zahav.net.il> (raw)
In-Reply-To: <20041105163933.GB8318@white> (message from Bob Rossi on Fri, 5 Nov 2004 11:39:33 -0500)
> Date: Fri, 5 Nov 2004 11:39:33 -0500
> From: Bob Rossi <bob@brasko.net>
> Cc: gdb-patches@sources.redhat.com
>
> +@node GDB/MI Handshaking Syntax
> +@subsection @sc{gdb/mi} Handshaking Syntax
> +
> +@cindex handshaking syntax for @sc{gdb/mi}
> +@cindex @sc{gdb/mi}, handshaking syntax
> +@table @code
> +@item @var{handshake_output} @expansion{}
> +@code{"handshake=@{stable_protocols=@{" @var{mi-protocol-list}
> +"@}" @var{nl}}
I think there's a need here for a cross-reference to the section that
explains the reason and principles of the handshaking (the other
section you wrote), otherwise this table looks awkwardly unexplained.
> +It is possible to start the @sc{gdb/mi} interpreter using -i=mi1, -i=mi2, or
> +simply with -i=mi.
The command-line options should be in @samp{} or in @option{}, like
this:
It is possible to start the @sc{gdb/mi} interpreter using @samp{-i=mi1}
Actually, instead of using literal mi1 and mi2, which could confuse
the reader into thinking that only MI1 and MI2 are supported (think
about someone reading this 10 years from now), I'd say
It is possible to start the @sc{gdb/mi} interpreter using
@samp{-i=mi@var{n}}, where @var{n} is the MI protocol version
(@pxref{Interpreters}). When invoked with a specific version of the
MI interpreter, @value{GDBN} will bypass the handshaking mode and go
directly into...
> +then this tells @value{GDBN} to go into it's handshaking mode with the
^^^^
This should be "its", without the apostrophe.
> +it supports. The term "stable MI protocol" simply means that the protocol
Please use ``this style'' to quote phrases in Texinfo (the result is
prettier in the printed version). Actually, in this case, since you
are introducing a new term, I'd suggest to say
The term @dfn{stable MI protocol} simply means...
Also, a @cindex entry here about stable MI protocol would be useful.
> +untested protocols, they could simply try to invoke @value{GDBN} with -i=miN,
> +where N is version they wish to communicate with.
Please use @var{n} instead of a literal "N" here.
> +If a specific version of @value{GDBN} speaks only one stable MI protocol than
The last woprd should be "then", not "than".
> +versions of the MI protocol, than it will output a list of these protocols
^^^^
Again, "then".
Other than these few minor problems, the documentation patch is
approved. Thanks.
next prev parent reply other threads:[~2004-11-05 17:50 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-04 19:57 Bob Rossi
2004-11-04 19:59 ` Bob Rossi
2004-11-11 20:30 ` Andrew Cagney
2004-11-12 3:44 ` Alain Magloire
2004-11-04 21:28 ` Eli Zaretskii
2004-11-05 16:39 ` Bob Rossi
2004-11-05 17:50 ` Eli Zaretskii [this message]
2004-11-05 22:12 ` Bob Rossi
2004-11-06 10:12 ` Eli Zaretskii
2004-11-08 14:49 ` Bob Rossi
2004-11-08 15:01 ` Eli Zaretskii
2004-11-12 9:54 Nick Roberts
[not found] <200411120344.WAA24018@smtp.ott.qnx.com>
2004-11-12 22:59 ` Andrew Cagney
2004-11-13 9:01 ` Eli Zaretskii
2004-11-13 13:48 ` Bob Rossi
2004-11-17 16:05 ` Alain Magloire
2004-11-17 16:32 ` Bob Rossi
2004-11-18 1:35 ` Alain Magloire
[not found] ` <200411180135.UAA14730@smtp.ott.qnx.com>
2004-11-19 19:23 ` Bob Rossi
2005-01-05 1:36 ` Bob Rossi
2005-01-05 1:51 ` Jim Ingham
2005-01-05 1:53 ` Bob Rossi
2005-01-05 2:01 ` Jim Ingham
2005-01-05 2:34 ` Bob Rossi
2005-01-05 2:40 ` Bob Rossi
2004-11-17 16:05 ` Alain Magloire
[not found] <200411171514.KAA17361@smtp.ott.qnx.com>
2004-11-17 17:30 ` Eli Zaretskii
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='01c4c35f$Blat.v2.2.2$3c749800@zahav.net.il' \
--to=eliz@gnu.org \
--cc=bob@brasko.net \
--cc=gdb-patches@sources.redhat.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