Users should switch to the superior AVFifo API. Unfortunately AVFifoBuffer fields cannot be marked as deprecated because it would trigger a warning wherever fifo.h is #included, due to inlined av_fifo_peek2().
Showing the changes to doc/APIchanges (1 of 4 files). Show all
Unified · Split
| @@ -14,6 +14,14 @@ libavutil: 2021-04-27 · 13 unmodified lines | ||
| 14 | 14 | |
| 15 | 15 | API changes, most recent first: |
| 16 | 16 | |
| 17 | +2022-02-07 - xxxxxxxxxx - lavu 57.21.100 - fifo.h | |
| 18 | + Deprecate AVFifoBuffer and the API around it, namely av_fifo_alloc(), | |
| 19 | + av_fifo_alloc_array(), av_fifo_free(), av_fifo_freep(), av_fifo_reset(), | |
| 20 | + av_fifo_size(), av_fifo_space(), av_fifo_generic_peek_at(), | |
| 21 | + av_fifo_generic_peek(), av_fifo_generic_read(), av_fifo_generic_write(), | |
| 22 | + av_fifo_realloc2(), av_fifo_grow(), av_fifo_drain() and av_fifo_peek2(). | |
| 23 | + Users should switch to the AVFifo-API. | |
| 24 | + | |
| 17 | 25 | 2022-02-07 - xxxxxxxxxx - lavu 57.20.100 - fifo.h |
| 18 | 26 | Add a new FIFO API, which allows setting a FIFO element size. |
| 19 | 27 | This API operates on these elements rather than on bytes. |