[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Feature request: generate documentation from C files
From: |
Karl Berry |
Subject: |
Re: Feature request: generate documentation from C files |
Date: |
Sun, 2 Nov 2003 10:27:40 -0500 |
I'm also unsure about legal status of it.
Hmm, we need to be clear on that before I can include it in Texinfo.
(Actually, we should really be clear even for linking, but anyway ...)
Is the original author(s) unknown?
I haven't convinced myself it is the right solution yet.
Sure, I know there are lots of considerations. Autodectecting
lists, examples, headings seems possible, maybe but I can't see how to
autodetect a simple variable name which should come out in tt and may
not have been previously seen.
Maybe some subset of pod? (perldoc perlpod) It is the most
minimal/simplest documentation format I know that is still reasonably
expressive.
"B<text>" -- bold text
"C<code>" -- code text
"L<name>" -- a hyperlink
=head1 Heading Text
=head2 Heading Text
=head3 Heading Text
=head4 Heading Text
=over indentlevel
There are pod2foo translators for a number of foo's.
- Re: Feature request: generate documentation from C files, Simon Josefsson, 2003/11/01
- Re: Feature request: generate documentation from C files, Karl Berry, 2003/11/01
- Re: Feature request: generate documentation from C files, Simon Josefsson, 2003/11/01
- Re: Feature request: generate documentation from C files, Eli Zaretskii, 2003/11/02
- Re: Feature request: generate documentation from C files, Simon Josefsson, 2003/11/02
- Re: Feature request: generate documentation from C files, Eli Zaretskii, 2003/11/02
- Re: Feature request: generate documentation from C files, Simon Josefsson, 2003/11/02
- Re: Feature request: generate documentation from C files, Eli Zaretskii, 2003/11/02
- Re: Feature request: generate documentation from C files, Eli Zaretskii, 2003/11/02
Re: Feature request: generate documentation from C files,
Karl Berry <=