Collectively, these trigger warnings in both Doxygen and
clang (-Wdocumentation-unknown-command). Weirdly, @p in doxygen doesn't do
anything but print in a fixed-width font anyway, so just use Markdown quotes to
replace it which has the same effect (and reads nicer in the source). The use
of @param like @p was invalid, so do the same to those.
The previous style(s) used in most places here violates the C standard, and in
practice can trigger -Wreserved-id-macro in clang for client code. So, switch
to a conventional style that doesn't trigger warnings (and is supported by
tools like clang-tidy).
types.h:
Remove the definition of `jack_native_thread_t` as we will be relying on
the one from systemdeps.h.
{jack,thread}.h:
Include systemdeps.h for definition of `jack_native_thread_t`.
jack_port_get_latency_range only returns meaningful values after ports get
connected, and that is signalled via the latency callback. Saying that it's
normally used in callbacks is too soft, the docs should make it clear that the
function is not very useful outside of the callback, because you don't know
whether the port is connected / whether the latency values changed.
This is semantically similar to jack_port_set_name() but because it is also passed a jack_client_t*, it can
contact the server to ensure that not only the rename is done but that port rename callbacks are delivered
appropriately
Nedko Arnaudov
David Robillard
David Runge
Maciej Bliziński
Andrew Kelley
Paul Davis