On 8 July 2016 at 14:18, Hendrik Leppkes wrote:
> On Fri, Jul 8, 2016 at 12:33 PM, Sami Hult wrote:
> > Let me rephrase: avio_put_str, which in my patch is used instead of
> > (forbidden) printf, outputs the terminating null-character with the
> string.
> >
>
> avio_put_str is intentionally desi
On Fri, Jul 8, 2016 at 12:33 PM, Sami Hult wrote:
> Let me rephrase: avio_put_str, which in my patch is used instead of
> (forbidden) printf, outputs the terminating null-character with the string.
>
avio_put_str is intentionally designed to write the null-character as
termination as well, since
Let me rephrase: avio_put_str, which in my patch is used instead of
(forbidden) printf, outputs the terminating null-character with the string.
On 8 July 2016 at 13:12, Sami Hult wrote:
> Hi all,
>
> metadata filter seems to output null-terminated strings (i.e.
> "frame:14\n\0pts:9\n\0"), which
Hi all,
metadata filter seems to output null-terminated strings (i.e.
"frame:14\n\0pts:9\n\0"), which I noticed first when trying to regex-match
them. Is this intended behavior and if it is, what is the rationale?
Sami
--
Mannilantie 37 B 11, 04400 58, tel. +358-46-539-6617
