Menu

#454 RG_INFO and RG_WARNING

Maybe
closed
internal (1)
1
2014-11-27
2014-10-22
Ted Felix
No

8/8/2014 it was agreed on the dev list that we should have RG_INFO and RG_WARNING macros to complement the existing RG_DEBUG macro.

RG_INFO would be used for startup and other low-volume, one-time information that should always be printed to the debug output even if RG_DEBUG is turned off via RG_NO_DEBUG_PRINT. It's important that these be very low-volume so that they don't interfere with debugging.

RG_WARNING would be used for unexpected but non-fatal error situations that we want logged to the debug output even if RG_DEBUG is turned off via RG_NO_DEBUG_PRINT. This will make it possible to turn off developer debugging (RG_DEBUG) but preserve a level of error reporting that might help in tracking down problems.

RG_WARNING and RG_INFO will essentially be the same: an RG_DEBUG that is immune to RG_NO_DEBUG_PRINT.

RG_DEBUG would be used for developer debugging and can be turned off with RG_NO_DEBUG_PRINT.

Discussion

  • Ted Felix

    Ted Felix - 2014-11-27

    Implemented in [r13804].

     

    Related

    Commit: [r13804]

  • Ted Felix

    Ted Felix - 2014-11-27
    • labels: --> internal
    • status: open --> closed
    • assigned_to: Ted Felix
     

Log in to post a comment.