mirror of
https://github.com/RIOT-OS/RIOT.git
synced 2024-12-29 04:50:03 +01:00
b5ea78ad47
For the caller there should be no difference if there is no message
in the queue and if there can't be a message in the queue.
The current API works as one would expect if there is a message queue,
but once called from a thread that does not have a message queue
configured, code that does
while (msg_avail())
will end up in an infinite loop.
Remove this foot-gun from the API by making the return value of
msg_avail() independend of the availability of a message queue.
|
||
|---|---|---|
| .. | ||
| include | ||
| assert.c | ||
| atomic_c11.c | ||
| atomic_sync.c | ||
| bitarithm.c | ||
| clist.c | ||
| cond.c | ||
| doc.txt | ||
| init.c | ||
| Kconfig | ||
| Makefile | ||
| mbox.c | ||
| msg_bus.c | ||
| msg.c | ||
| mutex.c | ||
| panic.c | ||
| priority_queue.c | ||
| ringbuffer.c | ||
| rmutex.c | ||
| sched.c | ||
| thread_flags.c | ||
| thread.c | ||