> > + \param flags A bitwise or of any number of the following: > + - \c SIGNAL_FLAG_QUEUING_REQUIRED: Signal queuing is > required. Fail > + instead of falling back to unqueued signals, when > queuing isn't > + possible. > + - \c SIGNAL_FLAG_SEND_TO_THREAD: Interpret the the given ID > as a > + \c thread_id rather than a \c team_id. Ignored when > the \a id is > + \code < 0 \endcode -- then the target is a process > group. > + \return \c B_OK on success, another error code otherwise. > I know you are working on Unix signal support which is great and it is tough for me to complain about but... you really shouldn't do this: \code < 0 \endcode because it will create a whole separate 100% width block in the documentation and it doesn't really get highlighted any differently in this particular case. You might want to use <tt> < 0 </tt> instead to put the text in a typewriter font. That does the same thing as \c but for multiple words. John Scipione