From: Wu Zhou <woodzltc@cn.ibm.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sources.redhat.com, Thomas.Koenig@online.de
Subject: Re: [RFC]: Patch to support Fortran derived type - Revised
Date: Tue, 22 Nov 2005 19:21:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.63.0511221512070.31199@linux.site> (raw)
In-Reply-To: <uk6f96jm2.fsf@gnu.org>
Hi Eli,
On Wed, 16 Nov 2005, Eli Zaretskii wrote:
> > Date: Wed, 16 Nov 2005 15:20:18 +0800 (CST)
> > From: Wu Zhou <woodzltc@cn.ibm.com>
> > cc: Thomas.Koenig@online.de
> >
> > I revised the patch to add derived type support. Now it can print
> > the nested type such like this:
> >
> > Type foo
> > int4 :: a
> > Type bar
> > real :: b
> > End Type bar :: x
> > End Type foo
> >
> > It could also handle the member access like q%x%b.
>
> Thanks.
>
> > Any more place is needed to be improved, please let me know.
>
> How about mentioning this in the manual? It would be good to document
> how these values and types are printed, in case a user is not fluent
> with these f9x features.
>
Thanks for your comments.
Yes. I am thinking of adding these to gdb manual. But I am not sure how
to organize them. As you know, we already have three subsection: Fortran
operators, Fortran defaults and special Fortran command. Which section
should this kind of text gets into? Maybe special Fortran commands?
But They are in fact common GDB command, only with somewhat different
output format. Maybe it make sense to add another new section? What do
you think?
However I did added a few words in the Fortran operators section. Here is
the patch:
Index: gdb.texinfo
===================================================================
RCS file: /cvs/src/src/gdb/doc/gdb.texinfo,v
retrieving revision 1.296
diff -u -p -r1.296 gdb.texinfo
--- gdb.texinfo 20 Nov 2005 06:12:59 -0000 1.296
+++ gdb.texinfo 22 Nov 2005 07:05:01 -0000
@@ -9159,6 +9159,10 @@ of the second one.
@item :
The range operator. Normally used in the form of array(low:high) to
represent a section of array.
+
+@item %
+Fortran 90 and afterwards use this to access the members of derived
+type, which is also introduced after the Fortran 90.
@end table
@node Fortran Defaults
Regards
- Wu Zhou
next prev parent reply other threads:[~2005-11-22 17:07 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 [this message]
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
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=Pine.LNX.4.63.0511221512070.31199@linux.site \
--to=woodzltc@cn.ibm.com \
--cc=Thomas.Koenig@online.de \
--cc=eliz@gnu.org \
--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