All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nathaniel Villaume <villaume@domain.hid>
To: Jan Kiszka <jan.kiszka@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-help] doc patch: RT_TASK_INFO
Date: Thu, 27 Jul 2006 11:40:10 -0700	[thread overview]
Message-ID: <44C9088A.20608@domain.hid> (raw)
In-Reply-To: <44C8EECE.4070209@domain.hid>

The patches were to help you out! I thought that maybe you wouldn't want 
RT_TASK documented -- users don't really need to konw about magic number 
and flowgen, do they?  But yeah, sorry for the spamming.

As for the comment style, the C style comments don't show up using this 
inline method: /*!< */   -- that was part of the original problem.  One 
solution is to use the @typedef command. The only drawback here is the 
minor replication. For example:

/*! @typedef RT_TASK
    @brief Contains important data
  @param  magic  Magic uniquely identifies the task's wizardry ancestry
  @param  prio   task priority
*/
typedef struct {
  int magic;  // Must come first!   (comments don't HAVE to go here)
  uint prio;  // task priority
  /* etc */
} RT_TASK;

What I need to know from you:
1) Do you care about this duplication of struct member-names (harder to 
keep docs synchronized with code)?
2) Do you want RT_TASK member documentation to show up in 
doxygen-generated pages?  (this lets me know what to change)

-Nate



  reply	other threads:[~2006-07-27 18:40 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200607271001.k6RA19sN018076@domain.hid>
2006-07-27 15:57 ` [Xenomai-help] doc patch: RT_TASK_INFO Nathaniel J Villaume
2006-07-27 16:50   ` Jan Kiszka
2006-07-27 18:40     ` Nathaniel Villaume [this message]
2006-07-27 19:26       ` Jan Kiszka
2006-07-27 18:58     ` [Xenomai-help] RT_TASK_INFO status Nathaniel Villaume
2006-07-27 19:26       ` [Xenomai-help] " Jan Kiszka
2006-07-27 22:45         ` Nathaniel Villaume
2006-07-28  9:04           ` Jan Kiszka
2006-07-28 13:51             ` Gilles Chanteperdrix
2006-08-01 18:46               ` Nathaniel Villaume
2006-08-02  6:13                 ` Jan Kiszka
2006-08-12 20:52                 ` Gilles Chanteperdrix
2006-07-28  9:09           ` Philippe Gerum
2006-07-27 16:23 ` [Xenomai-help] patch: native/task.h Nathaniel J Villaume
2006-07-27 16:27 ` [Xenomai-help] patch: info_mcb_changed_native_task.h.diff Nathaniel J Villaume
2006-07-27 16:28 ` [Xenomai-help] patch: all_changed_native_task.h.diff Nathaniel J Villaume

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=44C9088A.20608@domain.hid \
    --to=villaume@domain.hid \
    --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.