openh264/codec/encoder/core
Martin Storsjö 92fa4eb400 Use strlen instead of WelsStrnlen/STRNLEN for known null terminated strings
strlen is not dangerous if the string is known to be null
terminated (and MSVC does not warn about its use either).

For the cases in the decoder welsCodecTrace.cpp, the string
passed to all WriteString instances is produced by WelsVsnprintf
which always null terminates the buffer nowadays.

Additionally, as the string was passed to OutputDebugStringA
without any length specifier before, it was already assumed to
be null terminated.

The file name parameter passed to DumpDependencyRec and
DumpRecFrame in encoder.cpp is always null terminated,
which was already assumed as it is passed to WelsFopen as is.

As for the encoder utils.cpp, the strings returned by GetLogPath
are string constants that are null terminated.
2014-01-28 11:40:54 +02:00
..
asm Allow yasm to be used instead of nasm. 2014-01-18 13:59:24 +01:00
inc Merge pull request #235 from mstorsjo/merge-ls-defines 2014-01-27 14:10:00 -08:00
src Use strlen instead of WelsStrnlen/STRNLEN for known null terminated strings 2014-01-28 11:40:54 +02:00