Thread overview | |||||
---|---|---|---|---|---|
|
January 30, 2017 Why fatal log throw object.Error@(0) on console? | ||||
---|---|---|---|---|
| ||||
import std.stdio; import std.experimental.logger; void main() { sharedLog = new FileLogger("New_Default_Log_File.log"); fatal("Fatal error: "); } All other log-levels write as expected log files, but `fatal` throw on console: > app.exe object.Error@(0): A fatal log message was logged ---------------- 0x0041291E 0x004138E7 0x0040206C 0x0040B277 0x0040B178 0x00407AB3 0x73FC62C4 in BaseThreadInitThunk 0x77440FD9 in RtlSubscribeWnfStateChangeNotification 0x77440FA4 in RtlSubscribeWnfStateChangeNotification It's bug normal behavoiur? |
January 30, 2017 Re: Why fatal log throw object.Error@(0) on console? | ||||
---|---|---|---|---|
| ||||
Posted in reply to Suliman | I found in the docs mention "If data is logged with LogLevel fatal by default an Error will be thrown.". But what the reason of such behavior? |
January 30, 2017 Re: Why fatal log throw object.Error@(0) on console? | ||||
---|---|---|---|---|
| ||||
Posted in reply to Suliman | On 01/30/2017 05:21 AM, Suliman wrote:
> I found in the docs mention "If data is logged with LogLevel fatal by
> default an Error will be thrown.". But what the reason of such behavior?
That likely comes from the fact that 'fatal' describes states that you can't trust the program to do the right thing. For example, you may not be able to write to a log file. Fatal means fatal. :)
Ali
|
Copyright © 1999-2021 by the D Language Foundation