Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Wu Zhou <woodzltc@cn.ibm.com>
Cc: drow@false.org, gdb-patches@sources.redhat.com, Thomas.Koenig@online.de
Subject: Re: [RFC]: Patch to support Fortran derived type - Revised
Date: Sun, 11 Dec 2005 23:40:00 -0000	[thread overview]
Message-ID: <u8xute0kw.fsf@gnu.org> (raw)
In-Reply-To: <Pine.LNX.4.63.0512101455050.21855@linux.site> (message from Wu 	Zhou on Sat, 10 Dec 2005 15:24:29 +0800 (CST))

> Date: Sat, 10 Dec 2005 15:24:29 +0800 (CST)
> From: Wu Zhou <woodzltc@cn.ibm.com>
> cc: gdb-patches@sources.redhat.com, Thomas.Koenig@online.de
> 
> Here is the revised patch, testcase and documents.

Thanks.  My comments about the documentation patch are below.

> 2005-12-10  Wu Zhou  <woodzltc@cn.ibm.com>
> 
> 	* gdb.texinfo (Fortran): Document the "%" operator for member
> 	access.
> 	(Fortran): Document the type-print and value-print operation of
> 	Fortran 90 derived types.

These two entries reference the same node "Fortran", so there's no
need to mention the node twice.  Just write the two sentences one
after the other; you don't even need a newline between them.

> + @item %
> + ortran 90 and afterwards use this to access the members of derived
    ^^^^^^
A typo.

Also, I'd prefer "and later" instead of "and afterwards".

> + @cindex Structure type-print

Index entries by convention should begin with a lower-case letter.

> + Fortran 90 and afterwards support derived type (a.k.a structure).  For
               ^^^^^^^^^^^^^^
"and later"

> + a variable of derived type, ptype command will output all its members,
                                ^^^^^
Please give each command the @code markup: @code{ptype}.  Actually,
"the @code{ptype} command" is more correct English, I think.

> + @noindent
> + ptype commands give this output:
    ^^^^^^^^^^^^^^
"the @code{ptype} commands"

> + @end smallexample
> + 
> + @noindent
> + 

This @noindent looks unnecessary to me.  Why did you add it?

> + @cindex Structure value-print

Again, please begin all index entries with a lower-case letter.

> + @item print @var{derived-type}
> + For a variable of derived type, print command will output the value of
                                    ^^^^^^^^^^^^^
"the @code{print} command"

> + For example, for variable q of type foo defined above:

`q' and `foo' are Fortran symbols, so both of them should have the
@code markup: "for a variable @code{q} of type @code{foo} defined above".

> + @noindent
> + print command will output this:
    ^^^^^^^^^^^^^
"the @code{print} command"

> + $1 = @{ 3.125, @{ 1, 2.375@}, (97 'a', 98 'b', 99 'c', 100 'd', 101 'e', 102 'f', 103 'g')@}

This is too long for a single line (TeX will not break lines inside
@smallexample).  Please break it into 2 lines, and please add text
saying that it's a single long line, broken only for clarity.


  reply	other threads:[~2005-12-10  9:57 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-16 10:35 Wu Zhou
2005-11-16 14:16 ` Eli Zaretskii
2005-11-22 19:21   ` Wu Zhou
2005-11-22  9:36     ` Wu Zhou
2005-11-22 19:20       ` Daniel Jacobowitz
2005-11-23 13:06         ` Wu Zhou
2005-11-23  2:52     ` Eli Zaretskii
2005-12-08 10:33 ` Daniel Jacobowitz
2005-12-08 14:24   ` Eli Zaretskii
2005-12-08 19:22     ` Daniel Jacobowitz
2005-12-11 17:15   ` Wu Zhou
2005-12-11 23:40     ` Eli Zaretskii [this message]
2006-02-20 16:10     ` Daniel Jacobowitz
2006-02-24  7:53       ` Wu Zhou

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=u8xute0kw.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=Thomas.Koenig@online.de \
    --cc=drow@false.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=woodzltc@cn.ibm.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