Timeline for Struggle with catch 22 in initialization code
Current License: CC BY-SA 4.0
3 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 27, 2022 at 19:34 | comment | added | jaskij | I've hit something similar in my own code, and the point of using a logger to display errors early on was formatting - I wanted uniform formatting for errors which happen before the logger is initialized. And for initialization I need to know the log level, which is set in configuration. In the end, since a configuration error means the program dies soon after I ended up with parsing it first. | |
| Jun 26, 2022 at 18:57 | comment | added | Martin Maat | Yes. I do not see the point of insisting on having path find failures routed through your logger. Besides being pointless it is impossible. Suppose you run into an issue finding that path, you construct an error message and you do have an ILogger available. Where is it going to store that message? | |
| Jun 26, 2022 at 17:57 | history | answered | Greg Burghardt | CC BY-SA 4.0 |