> Maybe still add an assert() against the divisor != 0 before the code in the > other patch. > > Just so people in the future will know that if it does == 0 there is a logic > error elsewhere in the program. >
I don't like this idea, because it means we have to add an assert before any division, and before the usage of any * or -> ... Regards,
