Re: [RFA][patch 1/9] Yet another respin of the patch with initial Python support

[Tom Tromey <tromey at redhat dot com>]

>>>>> "Daniel" == Daniel Jacobowitz <drow@false.org> writes:

>> My rationale is simple: we should have a single chapter for scripting,
>> because that's where a reader would look for information on how to
>> write GDB scripts.  If there's sense to distributing this information
>> between separate chapters, please explain what that is.

Daniel> Ok, in that case I have an alternative suggestion: how about renaming
Daniel> the combined scripting chapter, and putting both Python scripting and
Daniel> the existing information in the new chapter?

I don't really want to merge them.  I don't think it provides much
benefit to the reader of the manual.

It might make sense to document the "python" command alongside
"define" or what have you -- but I think only barely, since the
"python" command is kinda pointless without the rest of the API.

In the long run the Python chapter is going to be 99% documentation of
the Python API, something that will hold little interest to the casual
gdb user.

I guess we could even go so far as to make a separate python API
manual.  That seemed like more of a pain though; I wasn't sure what
the benefit of that would be either.

Tom