Project

General

Profile

Necessary Maintenance #23594

Conflicting or repeated log levels

Added by Iker de Icaza Astiz over 1 year ago. Updated over 1 year ago.

Status:
New
Priority:
Low
Assignee:
-
Start date:
11/12/2019
Due date:
% Done:

30%

Estimated time:
Duration:

Description

Currently there are at least three places were log levels are defined, those in TRACE, the CAEN generator and CRT generator. They are mostly consistent between them, but with different names and less consistent for the higher values.
Is there any reason to have CAEN and CRT levels defined separately?


CAENs:
      TERROR    = 0,
      TWARNING  = 1,
      TINFO     = 2,
      TDEBUG    = 3,
      TCONFIG   = 4,
      TSTART    = 5,
      TSTOP     = 6,
      TSTATUS   = 7,
      TGETNEXT  = 8,
      TGETDATA  = 9,
      TMAKEFRAG = 10,
      TTEMP     = 30


CRT:
#define TR_ERROR 0
#define TR_WARNING 1
#define TR_LOG 2
#define TR_DEBUG 3

#define TR_GD_LOG 4
#define TR_GD_DEBUG 5

#define TR_FF_LOG 8
#define TR_FF_DEBUG 9

History

#1 Updated by Antoni Aduszkiewicz over 1 year ago

We've already changed CRT message levels to TLVL_ERROR etc. convention (which seems to be a standard). The only place where I see TR_ convention is ICARUS/PhysCrateData_generator

#2 Updated by Antoni Aduszkiewicz over 1 year ago

  • % Done changed from 0 to 30

Also available in: Atom PDF