On Tue, Mar 10, 2015 at 09:39:50AM +0100, Nicolas George wrote: > Le nonidi 19 ventôse, an CCXXIII, Michael Niedermayer a écrit : > > there should be a loop that replaces each sequence of any \n\r by a single > > crlf sequency > > > also ensure that one such sequence is at the end > > I believe this would be correct. > > > using no \r \n codes but only litteral bytes and > > This part would also be correct, but I believe it is completely unnecessary: > POSIX specifies the byte value of \r and \n (the C standard does not), and > AFAIK we never had bug reports that could even remotely be linked to that > issue. And seriously, if a compiler were to use different values, FATE would > fail all over the place immediately. > > It does not matter much, since this is equivalent, but I believe most C > programmers will find \n and \r much more readable than \012 and \015 or > even \x0a and \x0d; I do.
iam fine with either, i was just trying to be completely correct which may be overkill and indeed make the code less readable for no gain [...] -- Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB It is dangerous to be right in matters on which the established authorities are wrong. -- Voltaire
signature.asc
Description: Digital signature
_______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel