They might be different.

Callers are already checking if the pointer is NULL before using it.

This avoids a lot of duplicate code/ifdefs everywhere.

This code will not be evaluated if NDEBUG is defined

In the case of errors depending on network input (i.e. not programming
logic errors), we should report errors but not abort the application.
Assertions should be used to validate and document programmer
assumptions. Moreover, if assertions are deactivated at build-time, we
don't want our application to crash.

99 % of these are just whitespace changes. Some unnecessary includes
removed as well

try to make it more readable/understandable

sflphone-common -> daemon
sflphone-client-gnome -> gnome
sflphone-client-kde -> kde
sflphone-plugins -> plugins

Also the memory pool for the SDP must be deallocated after we've destroyed
the SDP.

(cherry picked from commit aeadc752)