Got rid of to-do in which I said I should get rid of NUM_CAST macro. I can't actually think of a good reason to get rid of it. "Macros are bad" is not a good reason of itself. In this case, NUM_CAST enables me to have the safety of boost::numeric_cast while debugging, and the speed of static_cast in release builds. I don't see how that's bad.
Got rid of to-do in which I said I should get rid of
NUM_CAST macro. I can't actually think of a good reason
to get rid of it. "Macros are bad" is not a good reason of
itself. In this case, NUM_CAST enables me to have the safety
of boost::numeric_cast while debugging, and the speed of
static_cast in release builds. I don't see how that's bad.


skybaboon/jewel