|Title||Assertions and run-time errors conflated|
|Assigned user||Gareth Rees|
|Description||Assertions should be things which the programmer believes will always be true. Other conditions are run-time errors and should have recovery code, and try not to be fatal errors in the replicator, as it has to be a reliable daemon or service.|
Assertions probably should be fatal, and provide plenty of backtrace information for debugging.
|Analysis||Clean up and carefully divide assertions from consistency checks and regularize the error recovery code.|
See also <
|Created by||Richard Brooksby|
|Created on||2000-11-22 12:48:09|
|Last modified by||Gareth Rees|
|Last modified on||2001-12-10 19:02:16|
|History||2000-11-22 RB Created from sources (see evidence).|
2000-12-07 RB Added analysis reference to e-mail.
|5389||closed||2000-12-04 18:45:31||Gareth Rees||Merged branch/2000-12-04/no-conflicts back into master sources.|
|5180||open||2000-11-30 15:21:24||Gareth Rees||I now use assert only for genuine assertions (indicating things that shouldn't be able to happen, like a function receiving an argument of the wrong type). Run-time errors are raised with an appropriate message, not asserted.|