| Age | Commit message (Collapse) | Author |
|---|
|
CVS patchset: 6071
CVS date: 2004/01/26 22:34:10
|
|
merging their CVS back to our copy
everyone please check, if your AAC samples still work
CVS patchset: 6024
CVS date: 2004/01/11 15:44:04
|
|
- some fixes to xine_decoder.c
CVS patchset: 5959
CVS date: 2003/12/30 02:00:10
|
|
CVS patchset: 4592
CVS date: 2003/04/12 14:58:46
|
|
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
|
|
makefile variable.
- Cleaned up Makefile.am (wine, goom, libxinevdec)
- Cleaned up compiler warnings (libfaad)
- Cleaned up header includes (libfaad, libdha)
CVS patchset: 4053
CVS date: 2003/01/31 01:20:24
|
|
CVS patchset: 3560
CVS date: 2002/12/16 18:59:50
|
|
CVS patchset: 2912
CVS date: 2002/10/22 04:48:41
|
|
CVS patchset: 2420
CVS date: 2002/08/09 22:36:36
|
