01adbfc605
FIXED: * logging package on Windows had a non-conformant GetLogger(). While this fix technically breaks API, this was a horribly broken thing so I'm including it as a minor bump instead of major and thus breaking SemVer. Too bad, so sad, deal with it; Go modules have versioning for a reason. The previous logging.GetLogger() behavior on Windows has been moved to logging.GetLoggerWindows().
28 lines
1.1 KiB
Plaintext
28 lines
1.1 KiB
Plaintext
- logging probably needs mutexes
|
|
|
|
- macOS support beyond the legacy NIX stuff. it apparently uses something called "ULS", "Unified Logging System".
|
|
-- https://developer.apple.com/documentation/os/logging
|
|
-- https://developer.apple.com/documentation/os/generating-log-messages-from-your-code
|
|
-- no native Go support (yet)?
|
|
--- https://developer.apple.com/forums/thread/773369
|
|
|
|
- The log destinations for e.g. consts_nix.go et. al. probably should be unexported types.
|
|
|
|
- add a `log/slog` logging.Logger?
|
|
|
|
- Implement code line/func/etc. (only for debug?):
|
|
https://stackoverflow.com/a/24809646
|
|
https://golang.org/pkg/runtime/#Caller
|
|
-- log.LlongFile and log.Lshortfile flags don't currently work properly for StdLogger/FileLogger; they refer to the file in logging package rather than the caller.
|
|
-- ZeroLog seems to be able to do it, take a peek there.
|
|
|
|
- StdLogger2; where stdout and stderr are both logged to depending on severity level.
|
|
- make configurable via OR bitmask
|
|
|
|
- Suport remote loggers? (eventlog, syslog, journald)
|
|
|
|
- JSON logger? YAML logger? XML logger?
|
|
|
|
- DOCS.
|
|
-- Done, but flesh out.
|