The behaviour of assert() is inconsistent. It depends on compilers e.g. assert()s may be ignored by msvc in Release mode.

This is an issue if we plan to use assert() as a way to stop when something go wrong.

At the same time some assert()s were inserted by developers. They are deemed useful when developing or unit testing.

We need to check the assert() calls and make sure we don't use it in the first case.
Review the use of assert() in the GPAC codebase
This is a GitHub Issue
repo:gpac
owner:gpac
Title : Review the use of assert() in the GPAC codebase
Issue date:

--- start body ---
The behaviour of assert() is inconsistent. It depends on compilers e.g. assert()s may be ignored by msvc in Release mode.

This is an issue if we plan to use assert() as a way to stop when something go wrong.

At the same time some assert()s were inserted by developers. They are deemed useful when developing or unit testing.

We need to check the assert() calls and make sure we don't use it in the first case.
--- end body ---
