|
From: Ethan A M. <merritt@u.washington.edu> - 2007-10-27 22:08:33
|
On Saturday 27 October 2007 13:18, Hans-Bernhard Br=F6ker wrote:
> Thomas Sefzick wrote:
>=20
> > who introduced the 'assert' statements into the 'GET_MIN' and 'GET_MAX'
> > macros and why?
>=20
> I did, for the reason assert() is pretty much always used: to ensure=20
> that worse, much harder to find problems don't appear further down the=20
> processing pipeline --- you did mention segfaults and strange=20
> wrap-around artifacts earlier...
=46or debugging - yes.
It would be more user friendly not to exit the program, however.
Instead it should be possible to disable the mouse interaction=20
until the next replot, and bail to the command line with an error
message int_error(). =20
Do you see any problems if the assert() statements were replaced by
if (whatever) {
[do something to disable mousing];
int_error(NO_CARET, "error message");
}
=2D-=20
Ethan A Merritt
|