Re: [patch] doc-python: Pretty Printing split user / developer

[Eli Zaretskii <eliz@gnu.org>]

> Date: Wed, 21 Apr 2010 22:50:46 +0200
> From: Jan Kratochvil <jan.kratochvil@redhat.com>
> 
> which I try to address by the attachment.  Is it OK this way?

Thanks.

> +@smallexample
> +(@value{GDBP}) print s
> +$1 = @{
> +  static npos = 4294967295, 
> +  _M_dataplus = @{
> +    <std::allocator<char>> = @{
> +      <__gnu_cxx::new_allocator<char>> = @{<No data fields>@}, <No data fields>@}, 
> +    members of std::basic_string<char, std::char_traits<char>, std::allocator<char> >::_Alloc_hider: 
> +    _M_p = 0x804a014 "abcd"
> +  @}
> +@}
> +@end smallexample

The long lines here need to be wrapped, to become shorter than 72
characters.

>  * Auto-loading::                Automatically loading Python code.
>  * Values From Inferior::
>  * Types In Python::		Python representation of types.
> -* Pretty Printing::		Pretty-printing values.
> +* Pretty Printing API::		Pretty-printing values.
>  * Selecting Pretty-Printers::   How GDB chooses a pretty-printer.
>  * Commands In Python::          Implementing new commands in Python.
>  * Functions In Python::         Writing new convenience functions.

This menu uses TAB characters.  Please convert all of them to spaces
("M-x untabify" in Emacs).  Using TABs in a Texinfo file is a no-no,
because it causes line misalignment in the Info output.

> +@value{GDBN} provides a mechanism to allow pretty-printing of values using
> +Python code.  The pretty-printer API allows application-specific code to
> +greatly simplify the display of complex objects.

This repeats what you just said in the "Pretty Printing" section.  I
don't think we need to repeat that.

Okay with these changes.