| Age | Commit message (Collapse) | Author |
|---|
|
All assert() function calls, with exceptions of libdvdread and libdvdnav, have been
replaced with XINE_ASSERT. Functionally XINE_ASSERT behaves just likes its predecesor but its
adding the ability to print out a stack trace at the point where the assertion fails.
So here are a few examples.
assert (0);
This use of assert was found in a couple locations most favorably being the default case of a switch
statement. This was the only thing there. So if the switch statement was unable to find a match
it would have defaulted to this and the user and the developers would be stuck wonder who died and where.
So it has been replaced with
XINE_ASSERT(0, "We have reach this point and don't have a default case");
It may seem a bit none descriptive but there is more going on behind the scene.
In addition to checking a condition is true/false, in this case '0', the XINE_ASSERT
prints out:
<filename>:<function name>:<line number> - assertion '<assertion expression>' failed. <description>
An example of this might be:
input_dvd.c:open_plugin:1178 - assertion '0' failed. xine_malloc failed!!! You have run out of memory
XINE_ASSERT and its helper function, print_trace, are found in src/xine-utils/xineutils.h
CVS patchset: 4301
CVS date: 2003/02/28 02:51:47
|
|
printf's, name the yuv_frames plugin properly
CVS patchset: 4235
CVS date: 2003/02/21 19:13:15
|
|
CVS patchset: 4082
CVS date: 2003/02/01 23:54:03
|
|
CVS patchset: 4078
CVS date: 2003/02/01 18:37:11
|
|
CVS patchset: 4066
CVS date: 2003/01/31 17:56:35
|
|
CVS patchset: 3988
CVS date: 2003/01/22 11:57:38
|
|
CVS patchset: 3972
CVS date: 2003/01/19 19:42:48
|
|
CVS patchset: 3969
CVS date: 2003/01/19 19:41:03
|
