This is not the first time that you advocate a wrong use of asserts, so please let me correct:
Le tridi 3 germinal, an CCXXIII, Luca Barbato a écrit : > Asserts are something you use while debugging to check for the impossible. Asserts are something you leave in your code to check for the impossible. > You do not want to crash, no matter how remote is the possibility. You want to crash when the impossible happens, because otherwise you are likely corrupting the users' data or opening a security breach. It is better for the users to read "assert failure" right now than "you have been pwned" months later. Of course, an assert that is known to be triggerable must be fixed. But asserts that are believed to be untriggerable are an additional safety and security measure, and must stay in the final code unless performance considerations mandate otherwise (and lavu has several levels of asserts for that). Regards, -- Nicolas George
signature.asc
Description: Digital signature
_______________________________________________ libav-devel mailing list [email protected] https://lists.libav.org/mailman/listinfo/libav-devel
