Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
    1. COI don't agree with (a), because `Warning` and `Error` are not verbs. Method names should be verbs by convention. `Warn` would be better, but how should we name methods that log errors and critical errors? `LogWarning` and `LogError` are IMO much better, or I'd rather use a generic method called `Log` with a `severity` argument that displays the type. While (b) could increase performance, most logging frameworks don't log in the background. It is tricky, and normally much safer to execute synchroniously.
      singulars
    2. COTheres also a rule that says that the class name should not be repeated in the method names. In this case it's all about taste since it's quite obvious that Error and LogError do the same thing. I prefer a Error method instead of a Log method with a severity parameter since it's less to type and read. But as I said: It's all about taste. (b) I don't see how writing to logs in a separate thread is tricky or unsafe. It's quite straight forward. A thread, a queue and a lock, nothing more is needed
      singulars
    3. COI didn't say it would be hard to implement; the thing is that logging is often an important part of a business process and in that case you don't want to continue processing before you know that your log message is persisted. Of course in other scenario's it could be fine to keep a queue of log messages. It depends. But for that reason logging frameworks usually process them synchronously.
      singulars
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload