-
Create a better logging solution than just haphazardly printing things
-
Motivation:
- To help understand newcomers how FSMLang works
- Could be used to test currently untested fragments of FSMLang (e.g file opening/saving, options, etc.) i.e. This features are inferred …
-
The codebase has ad hoc print statements and various LOGDEBUG type functions sprinkled throughout. It would be better to have a unified logging system with log levels (INFO, DEBUG, WARN) based on the …
-
Replace my current debug logging with the proper API
https://developer.apple.com/documentation/os/logging
-
-
**Describe the enhancement:**
Support for MacOS Unified Logging
**Describe a specific use case for the enhancement or feature:**
Auditbeat doesn’t provide much valuable information because it is …
-
Should allow for different levels:
debug, info, warning, error, critical
Also should write to file and to sterr. Output should be easily parsed so you can just view particular kinds of logs.
altf4 updated
12 years ago
-
Letting each individual module have its own logger makes actually turning all of them off a bear. Easiest solution would probably be to just have one unified logger gets passed around within the packa…
-
-
Should we propose a default mechanism for logging and settings?
Benefits IMO would be consistent behaviour for all ecosystem packages. Ideally there would be a way to set the logging level for all…