From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Jan Kiszka <jan.kiszka@domain.hid>
Cc: xenomai-core <xenomai@xenomai.org>
Subject: Re: [Xenomai-core] broken docs
Date: Sun, 5 Feb 2006 14:06:39 +0100 [thread overview]
Message-ID: <17381.63583.528140.947367@domain.hid> (raw)
In-Reply-To: <43E49D07.2070705@domain.hid>
Jan Kiszka wrote:
> Jan Kiszka wrote:
> > Gilles Chanteperdrix wrote:
> >> Looking at the difference between RTDM documentation blocks and the
> >> other modules is that the other modules use the "fn" tag. Removing the
> >> "fn" tag from other modules documentation blocks seems to solve the
> >> issue.
> >>
> >
> > Indeed, works. Amazingly blind I was.
> >
> > Anyway, it still needs some work to remove that stuff (I wonder what the
> > "correct" usage of @fn is...) and to wrap functions without bodies via
> > "#ifdef DOXYGEN_CPP" like RTDM does. At this chance, I would also
> > suggest to replace all \tag by @tag for the sake of a unified style (and
> > who knows what side effects mixing up both may have).
> >
>
> Here is a shell script aiming at an automated fix for parts of the
> mentioned issues. Anyone with better shell hacking skills may improve it
> (I'm always willing to learn!).
>
> for file in `find -name "*.[c|h]"`; do
> mv $file $file.tmp
> cat $file.tmp | (
> echo $file
> while read -r; do
> # delete " * @fn ..." lines
> new_line="`echo "$REPLY" | sed 's/\ \*\ @fn[^$]*$//' | \
> tr -d "\n"`"
> if echo "$REPLY" | grep -q '\ \*\ @fn[^$]*$'; then
> # delete empty comment lines succeeding " * @fn ..."
> read -r
> if [ "$REPLY" != " *" ]; then
> echo "$REPLY" >> $file
> fi
> else
> # convert " * \<tag>" to " * @<tag>"
> echo "$new_line" | sed 's/\ \*\ \\\([a-z]\)/ * @\1/' \
> >> $file
> fi
> done
> )
> rm $file.tmp
> done
>
>
> I only tested it on ksrs/skins/native, but it seems to work - for those
> functions with a body :-/. We still need to manually wrap body-less
> function docs as it is done in the rtdm skin. But I think this is a start.
The point is that the @fn tags improve readability of documentation
blocks, so, it would be nice if we could keep them. Simple tests with
the same Doxyfile as Xenomai show that the @fn tag works as expected, so
the problem may be due to something else. Now that I think about it,
the way we dealt with EXPORT_SYMBOL in Doxyfile is probably the culprit,
and the fix looks quite simple on elementary tests.
--
Gilles Chanteperdrix.
next prev parent reply other threads:[~2006-02-05 13:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-30 10:55 [Xenomai-core] broken docs ROSSIER Daniel
2006-01-30 12:17 ` Jan Kiszka
2006-01-30 12:40 ` Gilles Chanteperdrix
2006-01-30 12:59 ` Jan Kiszka
2006-02-04 12:24 ` Jan Kiszka
2006-02-05 13:06 ` Gilles Chanteperdrix [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-01-18 19:03 Jan Kiszka
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=17381.63583.528140.947367@domain.hid \
--to=gilles.chanteperdrix@xenomai.org \
--cc=jan.kiszka@domain.hid \
--cc=xenomai@xenomai.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.