diff options
author | Tom Tromey <tom@tromey.com> | 2023-02-07 21:40:53 -0700 |
---|---|---|
committer | Tom Tromey <tom@tromey.com> | 2023-02-15 10:27:34 -0700 |
commit | b8e81f19cbbe978c7376795129ee90ee8e73cf0a (patch) | |
tree | f276f24c72d208273ab89a597d74787cdea26689 /bfd/bfd.c | |
parent | fe20eda53c2bcc8182720978f7695b84efc9ec29 (diff) | |
download | gdb-b8e81f19cbbe978c7376795129ee90ee8e73cf0a.zip gdb-b8e81f19cbbe978c7376795129ee90ee8e73cf0a.tar.gz gdb-b8e81f19cbbe978c7376795129ee90ee8e73cf0a.tar.bz2 |
Use @deftypefn in chew output
When reading the BFD info manual, function definitions looked very
strange to me:
*Synopsis*
long bfd_get_mtime (bfd *abfd);
*Description*
Return the file modification time (as read from the file system, or from
the archive header for archive members).
The *Synopsis* and *Description* text in particular is very un-info-like.
To fix this, I tried removing the *Synopsis* text and having FUNCTION
use @deftypefn instead. However, this ended up requiring some new
state, because SYNOPSIS can appear without FUNCTION. This in turn
required "catstrif" (I considered adding FORTH-style if-else-then, but
in the end decided on an ad hoc approach).
After this the result looks like:
-- Function: long bfd_get_mtime (bfd *abfd);
Return the file modification time (as read from the file system, or
from the archive header for archive members).
This patch also reorders a few documentation comments to ensure that
SYNOPSIS comes before DESCRIPTION. This is the more common style and
is also now required by doc.str.
2023-02-07 Tom Tromey <tom@tromey.com>
* syms.c (bfd_decode_symclass, bfd_is_undefined_symclass)
(bfd_symbol_info): Reorder documentation comment.
* doc/doc.str (synopsis_seen): New variable.
(SYNOPSIS): Set synopsis_seen. Emit @deftypefn.
(DESCRIPTION): Use synopsis_seen.
* doc/chew.c (catstrif): New function.
(main): Add catstrif intrinsic.
(compile): Recognize "variable" command.
Diffstat (limited to 'bfd/bfd.c')
0 files changed, 0 insertions, 0 deletions