log4tango::LoggingEvent(3)

πŸ“¦
version 9.3.4 Β· 2 versions
, in debian bookworm

πŸ’– log4tango::LoggingEvent(3) πŸ’–

okay bestie, so this is the log4tango manual, section 3 (that's the library-functions girlies πŸ’…), and today's main character is log4tango::LoggingEvent. pull up a chair, grab a boba, we're doing this πŸ§‹βœ¨


✨ NAME ✨

log4tango::LoggingEvent β€” the internal representation of logging events. literally the vibe of a log message, bottled up and passed around. no cap.


🌸 SYNOPSIS 🌸

#include <LoggingEvent.hh>

πŸŽ€ Public Member Functions

  • LoggingEvent (const std::string &logger, const std::string &message, Level::Value level) β€” Instantiate a LoggingEvent from the supplied parameters. baby's first event 🐣
  • LoggingEvent (const LoggingEvent &event) β€” Copy constructor. twin energy, identical twins fr fr πŸ‘―

πŸ¦‹ Public Attributes

  • const std::string logger_name β€” The logger name. whose event is this? theirs. πŸ’…
  • const std::string message β€” The application supplied message of logging event. the actual tea being spilled β˜•
  • Level::Value level β€” Level of logging event. how loud are we being rn πŸ”₯
  • std::string thread_name β€” Name of thread in which this logging event was generated. which lil worker bee did this 🐝
  • long thread_id β€” id of thread in which this logging event was generated. same bee, but her number 🏷️
  • TimeStamp timestamp β€” The number of seconds elapsed since the epoch (1/1/1970 00:00:00 UTC) until logging event was created. the when. the era. the moment ⏰

πŸ’œ Detailed Description πŸ’œ

The internal representation of logging events. it's giving "I contain multitudes, but mostly your log line."

When a affirmative logging decision is made a LoggingEvent instance is created. This instance is passed around the different log4tango components. like a lil note being passed around class, except every component actually wants to read it πŸ“πŸ«Ά

This class is of concern to those wishing to extend log4tango. so if you're out here building your own appenders and being a lil extension icon, hi, this one's for you πŸ‘‘


πŸ‘‘ Constructor & Destructor Documentation πŸ‘‘

πŸ’« log4tango::LoggingEvent::LoggingEvent (const std::string & logger, const std::string & message, Level::Value level)

Instantiate a LoggingEvent from the supplied parameters. Except timeStamp all the other fields of LoggingEvent are filled when actually needed. so it's a lazy girlie and honestly? relatable. work smarter not harder ✨

Parameters

  • logger β€” The logger of this event.
  • message β€” The message of this event.
  • level β€” The level of this event.

πŸ’« log4tango::LoggingEvent::LoggingEvent (const LoggingEvent & event)

Copy constructor. that's it, that's the whole thing, she copies πŸ’…


🌈 Member Data Documentation 🌈

⭐ Level::Value log4tango::LoggingEvent::level

Level of logging event. the volume knob, basically πŸ”Š

⭐ const std::string log4tango::LoggingEvent::logger_name

The logger name. note the const bestie β€” once she's named, she's NAMED, no rebranding era 🚫

⭐ const std::string log4tango::LoggingEvent::message

The application supplied message of logging event. again const. the message is the message, periodt πŸ’–

⭐ long log4tango::LoggingEvent::thread_id

id of thread in which this logging event was generated

⭐ std::string log4tango::LoggingEvent::thread_name

Name of thread in which this logging event was generated. (see how she's not const? thread_name can get renamed mid-flight. growth era 🌱)

⭐ TimeStamp log4tango::LoggingEvent::timestamp

The number of seconds elapsed since the epoch (1/1/1970 00:00:00 UTC) until logging event was created. yes the epoch, the og reference point, the moment time itself said "and scene" πŸ•°οΈ


πŸ’€ Author πŸ’€

Generated automatically by Doxygen for log4tango from the source code. so technically the robot wrote it, but I'm the one delivering it with flair 🎀


heads up bestie: this page is auto-generated, so if something looks cursed in the ordering, that's Doxygen's doing, not mine πŸ™ˆ

and that's the whole page!! you understood it, I understood it, we all understood it. so iconic of us. 🫢

signing off from log4tango version 5.0.2, dated Thu Dec 5 2024 β€” that's the log4tango::LoggingEvent(3) girlies, we ate and left no crumbs πŸ’…βœ¨πŸŽ€

πŸ“¦ where this page comes from