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: gdb-patches@sources.redhat.com
Subject: Re: [RFC]: Document patch for F90 derived type support
Date: Fri, 24 Feb 2006 08:34:00 -0000	[thread overview]
Message-ID: <uek1t9nu6.fsf@gnu.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0602240250300.7628@localhost.localdomain> (message 	from Wu Zhou on Fri, 24 Feb 2006 02:54:16 -0500 (EST))

> Date: Fri, 24 Feb 2006 02:54:16 -0500 (EST)
> From: Wu Zhou <woodzltc@cn.ibm.com>
> 
> Here is the modified document patch for F90 derived type support.  Please 
> review and comment.

Reviewed; comments below.

> + Fortran 90 and later support derived type (a.k.a structure).  For a
                                               ^^^^^
This should be "a.k.a.@:".  You forgot the last period, and @: tells
TeX that this period does not end a sentence, so that TeX typeset it
correctly.

> + type = Type bar
> +     int4 :: c
> +     real*4 :: d
> + End Type bar

Btw, isn't it more consistent to print "integer*4" instead of "int4"?
Either that, or just "integer", I think.  Or is "int4" a valid type
name in f90?  (The last Fortran I used was f77, so please forgive my
ignorance.)

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

"q" and "foo" should be in @code (they are program symbols).

> + Please be noted that in the above example, the result of @code{print q}
    ^^^^^^^^^^^^^^^
"Please note".

Other than that, fine with me.  Thanks.


  reply	other threads:[~2006-02-24  8:13 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-24  8:13 Wu Zhou
2006-02-24  8:34 ` Eli Zaretskii [this message]
2006-02-27  5:59   ` Wu Zhou
2006-02-28  6:43     ` Eli Zaretskii
2006-02-28 15:05       ` Daniel Jacobowitz
2006-02-28 20:09         ` Eli Zaretskii
2006-03-01  2:51           ` Wu Zhou
2006-03-01  4:32             ` Daniel Jacobowitz
2006-03-01  4:53               ` Eli Zaretskii
2006-03-01  5:05                 ` Daniel Jacobowitz
2006-03-01 19:02                   ` Eli Zaretskii
2006-03-01 19:38                     ` Daniel Jacobowitz
2006-03-02  2:32                       ` Wu Zhou
2006-03-02  4:36                         ` Eli Zaretskii
2006-03-02  4:40                           ` Daniel Jacobowitz
2006-03-03  9:09                             ` Wu Zhou
2006-03-02  4:25                       ` Eli Zaretskii
2006-03-02  4:27                         ` Daniel Jacobowitz
2006-03-01  4:51             ` Eli Zaretskii
2006-03-02  2:43               ` Wu Zhou
2006-03-02  3:22                 ` Daniel Jacobowitz
2006-03-02  4:38                   ` Eli Zaretskii
2006-03-02  4:37                 ` 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=uek1t9nu6.fsf@gnu.org \
    --to=eliz@gnu.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