diff options
author | wm4 <wm4@nowhere> | 2014-10-28 14:46:55 +0100 |
---|---|---|
committer | wm4 <wm4@nowhere> | 2014-10-28 20:30:11 +0100 |
commit | 98356b81b4e2c1c5d86c3f1a2969a6db90c0718a (patch) | |
tree | bb809af674dc31e54a92371721b383a49d8271fd /demux/mf.c | |
parent | 0c0ff638a38a1354209413ba3546840ae2933444 (diff) | |
download | mpv-98356b81b4e2c1c5d86c3f1a2969a6db90c0718a.tar.bz2 mpv-98356b81b4e2c1c5d86c3f1a2969a6db90c0718a.tar.xz |
client API: clarify statement about thread-safety
The only reason for mpv_wait_event() not being thread-safe is that it
returns a pointer to a mpv_event struct member in the mpv_handle
context, which in turn is done for ABI-safety (user doesn't allocate or
manage the struct), and to avoid the need additional memory management.
Some users were interpreting this incorrectly.
Diffstat (limited to 'demux/mf.c')
0 files changed, 0 insertions, 0 deletions