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: gdb.texinfo is getting too big


> Date: Wed, 16 Oct 2013 20:52:41 +0100
> From: Pedro Alves <palves@redhat.com>
> CC: Doug Evans <dje@google.com>, gdb-patches@sourceware.org,
>         stan@codesourcery.com
> 
> Maybe it'd be easier to think in terms of things that would make
> sense to split out of the main file.  E.g., the RSP chapter is useful
> for GDB and stub developers, but not for regular users -- split that
> one out.  Python scripting API stuff is useful for advanced users
> that want to extend GDB, but it's not really the same class of manual
> as the other chapters, so split that one out as another file too.
> MI is useful for frontend writers, not for regular users, so out it
> goes too.  Whatever other identifiable logic units we find, split
> them out.  Then I suspect we'll end up with the core manual for
> regular users that describes GDB's main features/CLI/commands,
> and it'll be lean enough to be manageable.

You are talking about splitting the manual, whereas Doug was talking
about splitting the sources while keeping a single manual as output.

I'm not sure I see a good reason to split the manual.  For starters,
the size of that doesn't hurt as much as the size of the source file
when you need to edit it.


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