This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [rfc] python API exposing inferior's frame stack.
> Cc: Thiago Jung Bauermann <bauerman@br.ibm.com>, gdb-patches@sourceware.org
> From: Tom Tromey <tromey@redhat.com>
> Date: Tue, 17 Mar 2009 15:01:23 -0600
>
> >>>>> "Eli" == Eli Zaretskii <eliz@gnu.org> writes:
>
> >> +@tindex gdb.Frame
> >> +@tindex Frame
>
> Eli> Please don't use @tindex, we don't use such an index in the GDB
> Eli> manual.
>
> Now that we have documentation describing types, it seems like we
> ought to add a type index.
What's wrong with having them documented in the main index? We can
always have something like
@cindex @code{Foo}, a data type
More than one index in a manual complicates looking up things, and I
don't feel the number of types we have in GDB, or will have in the
near future, justifies this inconveniency. But I'm open to arguments
to the contrary.