This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
Re: Thoughts? New chapter: ``Advanced Features''
- From: Robert Lopez <robert dot lopez at abq dot sc dot philips dot com>
- To: ac131313 at cygnus dot com, eliz at is dot elta dot co dot il
- Cc: gdb at sources dot redhat dot com
- Date: Fri, 15 Mar 2002 11:20:22 -0700 (MST)
- Subject: Re: Thoughts? New chapter: ``Advanced Features''
- Reply-to: Robert Lopez <robert dot lopez at abq dot sc dot philips dot com>
> From: "Eli Zaretskii" <eliz@is.elta.co.il>
> > What do people think of creating a new chapter ``Advanced Features''
> > and moving this stuff to there.
>
> I'm not sure this is a good idea. It makes sense to do this in a
> manual that is divided into two large parts: a tutorial and the
> ``advanced'' part. But the GDB manual is not like that: most of its
> features are described outside the tutorial. So having an advanced
> chapter would mark those commands as being out of limits for
> ``plebeians'', which is not something I think we want to say.
I understand the artificial limit you bring up. It is a good thought.
But most tools do have the general features and the advanced features.
I see no harm in the catagories so long as they are not wrong.
>
> > If we don't, I get the feeling that the GDB documentation will just
> > continue to accumulate lots of small chapters
>
> The manual in v5.1.1 has 28 chapters. This is not too much (IMHO);
> for example, Emacs has 32 chapters and 7 large appendices, i.e. 39
> chapters altogether.
>
> But if people feel 28 is too much, I don't mind restructuring the
> manual into fewer chapters. I don't think it would be very hard.
I have no problem with the current manual organization. So I have no
problem with the number of chapters. I do not think that is an issue.
What I really did like was the general and advanced idea and
especially the idea about
| feature
| tutorial
| reference
grouping of information with lots of examples.