From: "Eli Zaretskii" <eliz@elta.co.il>
To: brobecker@gnat.com
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA/doco] Add documentation for observer.[hc] (gdbint.texinfo)
Date: Sun, 09 Mar 2003 16:10:00 -0000 [thread overview]
Message-ID: <3942-Sun09Mar2003180333+0200-eliz@elta.co.il> (raw)
In-Reply-To: <20030309065155.GB966@gnat.com> (message from Joel Brobecker on Sat, 8 Mar 2003 22:51:55 -0800)
> Date: Sat, 8 Mar 2003 22:51:55 -0800
> From: Joel Brobecker <brobecker@gnat.com>
>
> The following patch adds some light documentation about the new observer
> paradigm introduced recently.
Thanks. A few minor comments below.
> * gdbint.texinfo: Fix a small typo.
> (Observing Changes in GDB internals): New section.
> (GDB Observers currently available): Add menu entry to new appendix.
ChangeLog entries for the manuals should mention node names, not
section names.
> @tex
> ! \def\$#1${{#1}} % Kluge: collect RCS revision info without $...$
> \xdef\manvers{\$Revision$} % For use in headers, footers too
> {\parskip=0pt
> \hfill Cygnus Solutions\par
> --- 40,46 ----
> @author Cygnus Solutions
> @page
> @tex
> ! \def\$#1${{#1}} % Kludge: collect RCS revision info without $...$
I'm not sure we should make this change: there are more than a single
way to spell that word. (It originates from German, AFAIK, where
"Kluge" is the correct spelling.)
> + * GDB Observers:: @value{GDBN} Observers currently available
I think "Currently available observers" is more English-like ;-)
> + @section Observing changes in @value{GDBN} internals
> + @cindex observer
An index entry that says just "observer" will not be helpful, I
think. How about the following entries instead?
@cindex observer pattern interface
@cindex notifications about changes in internals
> + The rationale for the current implementation of the Observer pattern
> + is described in @file{observer.c}.
I'd suggest to copy that rationale from observer.c into the manual.
> @appendix @value{GDBN} Observers currently available
>
> @section @code{normal_stop} Notifications
>
> @value{GDBN} will notify all @code{normal_stop} observers when the
> inferior execution has just stopped and the @value{GDBN} prompt is
> about to be returned to the user.
I suggest an index entry before the last paragraph. Something like
this:
@cindex @code{normal_stop} observer
@cindex notification about inferior execution stop
next prev parent reply other threads:[~2003-03-09 16:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-09 6:51 Joel Brobecker
2003-03-09 15:36 ` Daniel Jacobowitz
2003-03-10 14:41 ` Andrew Cagney
2003-03-10 18:46 ` Joel Brobecker
2003-03-09 16:10 ` Eli Zaretskii [this message]
2003-03-10 19:01 ` Joel Brobecker
2003-03-10 20:04 ` 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=3942-Sun09Mar2003180333+0200-eliz@elta.co.il \
--to=eliz@elta.co.il \
--cc=brobecker@gnat.com \
--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