[FFmpeg-cvslog] lavc: clarify thread_safe_callbacks doxy

Anton Khirnov git at videolan.org
Mon Mar 8 12:36:11 EET 2021


ffmpeg | branch: master | Anton Khirnov <anton at khirnov.net> | Tue Mar  2 10:08:08 2021 +0100| [54e5d21acabb452e5680de5db3bf7567d351d68e] | committer: Anton Khirnov

lavc: clarify thread_safe_callbacks doxy

State explicitly when this field will be removed and how to access it in
a forward compatible way.

> http://git.videolan.org/gitweb.cgi/ffmpeg.git/?a=commit;h=54e5d21acabb452e5680de5db3bf7567d351d68e
---

 libavcodec/avcodec.h | 6 +++++-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/libavcodec/avcodec.h b/libavcodec/avcodec.h
index 46d31b34ad..3ecb3a4a60 100644
--- a/libavcodec/avcodec.h
+++ b/libavcodec/avcodec.h
@@ -1797,7 +1797,11 @@ typedef struct AVCodecContext {
      *
      * @deprecated the custom get_buffer2() callback should always be
      *   thread-safe. Thread-unsafe get_buffer2() implementations will be
-     *   invalid once this field is removed.
+     *   invalid starting with LIBAVCODEC_VERSION_MAJOR=60; in other words,
+     *   libavcodec will behave as if this field was always set to 1.
+     *   Callers that want to be forward compatible with future libavcodec
+     *   versions should wrap access to this field in
+     *     #if LIBAVCODEC_VERSION_MAJOR < 60
      */
     attribute_deprecated
     int thread_safe_callbacks;



More information about the ffmpeg-cvslog mailing list