• Marvin Scholz's avatar
    avformat: do not use AVIO_FLAG_* with avio_alloc_context · c6f4e101
    Marvin Scholz authored
    The documentation states that here 0 should be used for read-only and
    1 for a writable buffer. AVIO_FLAG_WRITE however is 2, while it works
    due to the way the flag is handled internally, it is still wrong
    according to the documentation.
    
    Additionally it makes it seem as if the AVIO_FLAG_* values could be used
    here, which is actually not true, as when AVIO_FLAG_READ would be used
    here it would create a writable buffer as AVIO_FLAG_READ is defined as 1.
    Signed-off-by: 's avatarAnton Khirnov <anton@khirnov.net>
    c6f4e101
Name
Last commit
Last update
compat Loading commit data...
doc Loading commit data...
ffbuild Loading commit data...
fftools Loading commit data...
libavcodec Loading commit data...
libavdevice Loading commit data...
libavfilter Loading commit data...
libavformat Loading commit data...
libavutil Loading commit data...
libpostproc Loading commit data...
libswresample Loading commit data...
libswscale Loading commit data...
presets Loading commit data...
tests Loading commit data...
tools Loading commit data...
.gitattributes Loading commit data...
.gitignore Loading commit data...
.mailmap Loading commit data...
.travis.yml Loading commit data...
CONTRIBUTING.md Loading commit data...
COPYING.GPLv2 Loading commit data...
COPYING.GPLv3 Loading commit data...
COPYING.LGPLv2.1 Loading commit data...
COPYING.LGPLv3 Loading commit data...
CREDITS Loading commit data...
Changelog Loading commit data...
INSTALL.md Loading commit data...
LICENSE.md Loading commit data...
MAINTAINERS Loading commit data...
Makefile Loading commit data...
README.md Loading commit data...
RELEASE Loading commit data...
configure Loading commit data...