From: James Courtier-D. <Ja...@su...> - 2003-03-26 01:19:39
|
Stephen Torri wrote: >On Tue, 2003-03-25 at 18:59, James Courtier-Dutton wrote: > > > >>Summary: - >>We should define what we are trying a achieve with xine_assert() before >>people dis it. >> >>Cheers >>James >> >> > >My whole intention in using this XINE_ASSERT() or xine_assert() was to >provide a more intelligent reason of why I reach that point in the code. >I try to "idiot" proof my code so that when I am programming while being >tired I obtain help from these messages of why my 'for' is not working >properly for example. Also I try to alert myself as to what function >caused this problem. This helps me hunt down the affect area and also >prevents me getting confused if I have repeative uses of the same assert >in the code: assert(0) is an example. > >Stephen > > If you do an assert(0), it will print out the line number and source code file that contained the assert(0). Why is that not enough. I sometimes added a printf() in front of the assert(0) if I really needed it, but that is quite rare. Cheers James |