On 3/21/2021 8:13 PM, Hendrik Leppkes wrote:
On Sun, Mar 21, 2021 at 3:24 PM James Almer <jamr...@gmail.com> wrote:
How about adding the deprecation attribute to prompt people to read the
doxy, where we state the field is not going away, just changing types?
Otherwise i don't think people will notice.
I really don't like such solutions. You get warning spam in user code
with basically no way to remedy them.
- Hendrik
I'm going to add a new field in the end. A change of type can't ensure
projects that don't migrate stop compiling (Like it happens when a field
is removed), and instead will unexpectedly crash if they try to access
it the wrong way.
But i can't do it until after the bump because libavdevice is locking
every AVStream field offset.
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
