{"repo":"KjellKod/g3log","free":true,"listed":false,"github":"https://github.com/KjellKod/g3log","clone":"git clone https://github.com/KjellKod/g3log.git","description":"G3log is an asynchronous, \"crash safe\", logger that is easy to use with default logging sinks or you can add your own. G3log is made with plain C++14 (C++11 support up to release 1.3.2) with no external libraries (except gtest used for unit tests). G3log is made to be cross-platform, currently running on OSX, Windows and several Linux distros. See Readme below for details of usage.","language":"C++","stars":960,"topics":["c-plus-plus","logger","logging","crash-safe","crash-reporting","asynchronous","async","public-domain"],"license":"Unlicense","category":"analytics","readme_excerpt":"Scanning Update : Contents introduction detailed information Configure & Build API description Custom log formatting Welcome to g3log Use kjellkod.github.io/g3log/ for best reading / searching / navigating of g3log's documentation G3log is an asynchronous logger with three main features: 1. Intuitive LOG(...) API 2. Design-by-contract CHECK(...) functionality 3. Fatal crash handling for graceful shutdown of the logged process without loosing any log details up to the point of the crash. The super quick introduction to g3log can be seen in the steps 1 - 9 below. For more in-depth information please see the full usage description in g3log usage.md. If you want to understand better the internals of g3log, then plase look at the API.md for both high-level and deep-dive insights. Experiment and try-out g3log in Github Codespaces ref: codespaces.md 1. Easy usage in files Avoid deep dependency injection complexity and instead get access to the logger as easy as: 2. Access to streaming and print f log call syntax Both streaming syntax LOG and print f LOGF syntax are available: 3. Conditional logging 4. Design-by-contract framework 5. Handling of fatal By default g3log will capture fatal events such as LOG(FATAL) , CHECK(false) and otherwise fatal signals such as: When a fatal event happens the not-yet written log activity will be flushed to the logging sinks. Only when all logging activity up to the point of the fatal event has happened, will g3log allow the fatal event to proceed an","default_branch":null,"files":null,"tree":[],"storefront":"/r/KjellKod","claimed":false,"request_supported":{"post":"https://gitbuyer.com/r/KjellKod/g3log/request-supported","requests":0},"note":"indexed from public GitHub; nothing is for sale on this page. Clone it from GitHub. Paid listings live at /search."}