This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [RFC]: Document patch for F90 derived type support


> Date: Sun, 26 Feb 2006 23:34:40 -0500 (EST)
> From: Wu Zhou <woodzltc@cn.ibm.com>
> cc: gdb-patches@sources.redhat.com
> 
> > > + 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.)
> 
> Yes. I also think so.  But the name of "int4" is got from the DWARF tag:
> 
>  <1><e6>: Abbrev Number: 4 (DW_TAG_base_type)
>      DW_AT_name        : int4
>      DW_AT_byte_size   : 4
>      DW_AT_encoding    : 5      (signed)

Well, we don't need t print everything DWARF-2 throws at us verbatim.
If you agree with my suggestions, I say let's use them.  Are there any
problems with that?

> + For a variable of derived type, the @code{print} command will output the
> + value of all its members, including its nested derived type .
                                                               ^^
An extra space.

> + Please note that in the above example, the result of @code{print q} is

@kbd{print q}, since it's what the user types at her keyboard.

Otherwise okay, thanks.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]