Category: С++
11 Jul 2026
Migrating from glog to logme: LOG, CHECK, PLOG, and VLOG in a New Logging Model
Migrating from glog to logme does not have to start with a full rewrite of every logging call. In large C++ projects, that is usually the wrong first step. Logging statements are spread across the codebase, and they often sit next to checks, conditions, diagnostic messages, CHECK, PLOG, VLOG, and debug-only calls. Replacing everything at
09 Jul 2026
logme channels are more than named loggers
At first, logme channels can look like ordinary logger names. You may have channels such as HTTP, DB, TLS, or UI. At first glance, each log call seems to add nothing more than the corresponding label. A channel is a full runtime object. It decides whether a record is accepted, how it is formatted. Where
07 Jul 2026
C++ Logging Macros: Why Are They So Complicated?
When developers first look at a modern C++ logging library, one thing often surprises them: the number of macros. At first glance, this raises an obvious question: why are there so many of them? Wouldn’t one clean Log() function be enough? Yet libraries such as logme provide dozens of variants, including LogmeI, LogmeW, LogmePV, fLogmeD,
21 Jun 2026
Manage Diagnostics Without Restarting
Runtime logging control is especially important for production services. Detailed debug logs are most useful when something has already gone wrong. However, keeping them enabled all the time is usually not acceptable. Verbose logs create noise. They increase file size. They can slow down hot code paths. In some cases, they may also expose details