Subj : loglevels
To   : andrew clarke
From : Kai Richter
Date : Sat Feb 27 2021 16:19:12

Hello andrew!

27 Feb 21, Michael Dukelsky wrote to andrew clarke:

 ac>> scanarea.c:       w_log(LL_START, "Scanning area: %s",

 ac>> At first glance this a bug, and "LL_START" should be "LL_SCANNING".

 MD> I also think this is a bug. LL_START should be used at the beginning
 MD> of a function and before every "return" from it.

Hm, from what the user documentation said i would expect level 1 to record the start of a module (hpt, htick, hptsqix, nltool...). More LogLevel is needed for troubleshooting only. Once the software is working well, i would like to see a confirmation that it was started to make sure previous scripts did their job.

Are there other locations in the source where LL_SCANNING is used to control output?

The husky loglevels system is other that software that defines a single loglevel which includes all lower LL. Husky does it more detailed like "turn level X on/off seperately". May that's why it's called LogLevel*s* and not LogLevel, i didn't noticed that fine difference in the keyword before.

Regards

Kai

--- GoldED+/LNX 1.1.4.7
 * Origin:  Monobox  (2:240/77)

.