Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Eli Zaretskii" <eliz@is.elta.co.il>
To: ac131313@cygnus.com
Cc: gdb-patches@sources.redhat.com
Subject: Re: [rfa/doc] Update ui-out; Was: [patch] Add col_name to ui_out_table_header()
Date: Fri, 06 Jul 2001 22:53:00 -0000	[thread overview]
Message-ID: <3405-Sat07Jul2001084846+0300-eliz@is.elta.co.il> (raw)
In-Reply-To: <3B4639A2.2070205@cygnus.com>

> Date: Fri, 06 Jul 2001 18:20:18 -0400
> From: Andrew Cagney <ac131313@cygnus.com>
> 
> I think I got all of these.  Keep an eye out for the @pxref{} and 
> @footnote{}.

I did.  Here's a couple of minor comments.

> ! Most @code{ui_out} routines are of type @code{void}, The exceptions are

"The" should be "the".

> ! To recap: A @dfn{tuple} is a sequence of @dfn{fields}, each field
> ! containing information about an object; a @dfn{list} is a sequence of
> ! @dfn{fields} where each field describes an identical object.

The second "fields" should not be inside a @dfn, since we already have
one here.

> ! and correct implementation of the non-portable @footnote{The function
> ! cast is not portable ISO-C.} code sequence:

@footnote should immediately follow the letter after which you want
the footnote marker in the printed version, because otherwise TeX will
keep the blank between the footnote and the preceding text.  So:

  and correct implementation of the non-portable@footnote{The function


  reply	other threads:[~2001-07-06 22:53 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-21  8:37 Andrew Cagney
2001-06-22  1:35 ` Eli Zaretskii
2001-07-04 17:30   ` [rfa/doc] Update ui-out; Was: " Andrew Cagney
2001-07-04 23:54     ` Eli Zaretskii
2001-07-05 19:40       ` Andrew Cagney
2001-07-06  1:31         ` Eli Zaretskii
2001-07-06 15:20       ` Andrew Cagney
2001-07-06 22:53         ` Eli Zaretskii [this message]
2001-07-07  9:16           ` Andrew Cagney
2001-07-07  9:56             ` 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=3405-Sat07Jul2001084846+0300-eliz@is.elta.co.il \
    --to=eliz@is.elta.co.il \
    --cc=ac131313@cygnus.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