Modified behavior of ASSERT, DEBUG_PRINT, and DEBUG_PRINT_VAR
Modified behavior of ASSERT, DEBUG_PRINT, and DEBUG_PRINT_VAR

To avoid generating huge logging files when running larger test problems,
DEBUG_PRINT and DEBUG_PRINT_VAR are now only active when DEBUG is set to
a value greater than 1. As before, the ASSERT macro is always active when
DEBUG is defined.

bsilbaugh/NumLib,bsilbaugh/NumLib,bsilbaugh/NumLib,bsilbaugh/NumLib