Re: [PATCH 06/25] Generate c for feature instead of tdesc

[Eli Zaretskii <eliz at gnu dot org>]

> From: Yao Qi <qiyaoltc@gmail.com>
> Cc: gdb-patches@sourceware.org
> Date: Thu, 15 Jun 2017 14:19:25 +0100
> 
> I update the paragraph for this command a little bit,
> 
> @kindex maint print c-tdesc @r{[}@var{file}@r{]}
> @item maint print c-tdesc
> Print the target description (@pxref{Target Descriptions}) as
> a C source file.  By default, the target description is for the current
> target, but if the optional argument @var{file} is provided, that file
> is used to produce the description.  The @var{file} should be an XML
> document, of the form described in @ref{Target Description Format}.
> The created source file is built into @value{GDBN} when @value{GDBN} is
> built again.  This command is used by developers after they add or
> modify XML target descriptions.

Thanks, this is good.

> > If we remove them, there will be no place where they are documented,
> > right?  GDB developers are GDB users as well, e.g. I read the manual
> > quite a lot.
> >
> > So I see no reason to remove these commands.  We just need to indicate
> > when a command makes sense only for GDB developers.
> 
> but GDB users are not GDB developers.  Why does user manual documents
> some commands users never use?

Because I expect GDB developers to look for commands they need to use
in this manual.

> IMO, these documents should be documented in GDB internals.

AFAIU, GDB internals documents the GDB implementation, not commands
and options that are used interactively within GDB.