Re: [xine-devel] xine's console output

[Stephen T. <st...@sb...>]

On Sun, 2003-03-09 at 17:35, Daniel Caujolle-Bert wrote:
> Hi,
>=20
> Mark Thomas wrote:
> > On Fri, 7 Mar 2003, Guenter Bartsch wrote:
> >=20
> >=20
> >>>ok, but.... how does the shinny new assert macro fits into these codin=
g
> >>>style rules?
> >>
> >>do you remember how i tried to keep it from happening? :-D
> >>
> >=20
> >=20
> > This sort of logging is fine for an inline function (remember, we only
> > *needed* a macro for XINE_ASSERT because we wanted the line number,
> > function name, and a stringified copy of the expression---all stuff tha=
t
> > can only really be done in the preprocessor).
>=20
> 	Did you ever used assert() ? It print already these informations.
>=20

True yet as the conversation over XINE_ASSERT when on the ideas of what
our version of assert would do expanded. In the end we wanted:

assert() + Descriptive failure message + backtrace.

Stephen
--=20
Stephen Torri <st...@sb...>