log4cpp::LoggingEvent(3)

πŸ“¦
version 1.1.4 Β· 3 versions
, in opensuse-leap 16.0

πŸ’– log4cpp::LoggingEvent(3) β€” Library Functions Manual πŸ’–

okay bestie, this is the Library Functions Manual page for log4cpp::LoggingEvent(3). ngl, it's giving very "internal plumbing but make it cute" energy. 🫢

✨ NAME ✨

log4cpp::LoggingEvent β€” the internal representation of logging events. periodt, that's the whole name section.

πŸ¦‹ SYNOPSIS πŸ¦‹

#include <LoggingEvent.hh>

🌸 Public Member Functions 🌸

  • LoggingEvent (const std::string &category, const std::string &message, const std::string &ndc, Priority::Value priority) β€” instantiate a LoggingEvent from the supplied parameters. iconic constructor behavior, no cap.

πŸŽ€ Public Attributes πŸŽ€

  • const std::string categoryName β€” the category name.
  • const std::string message β€” the application supplied message of logging event.
  • const std::string ndc β€” the nested diagnostic context (NDC) of logging event.
  • Priority::Value priority β€” priority of logging event.
  • const std::string threadName β€” the name of thread in which this logging event was generated, e.g.
  • TimeStamp timeStamp β€” the number of seconds elapsed since the epoch (1/1/1970 00:00:00 UTC) until logging event was created.

🌟 Detailed Description 🌟

okay so the big vibe: log4cpp::LoggingEvent is the internal representation of logging events. That's the main character energy of this whole class. πŸ’…

When an affirmative logging decision is made, a LoggingEvent instance is created. This instance is literally passed around the different log4cpp components. fr fr, it gets around.

This class is of concern to those wishing to extend log4cpp. iykyk β€” if you're extending log4cpp, this is your moment. πŸ¦‹

πŸ”₯ Constructor & Destructor Documentation πŸ”₯

log4cpp::LoggingEvent::LoggingEvent

log4cpp::LoggingEvent::LoggingEvent (const std::string & category, const std::string & message, const std::string & ndc, Priority::Value priority) β€” instantiate a LoggingEvent from the supplied parameters. Except timeStamp all the other fields of LoggingEvent are filled when actually needed. lowkey efficient, highkey iconic.

Parameters

  • category β€” the category of this event.
  • message β€” the message of this event.
  • ndc β€” the nested diagnostic context of this event.
  • priority β€” the priority of this event.

🧚 Member Data Documentation 🧚

const std::string log4cpp::LoggingEvent::categoryName

the category name.

const std::string log4cpp::LoggingEvent::message

the application supplied message of logging event.

const std::string log4cpp::LoggingEvent::ndc

the nested diagnostic context (NDC) of logging event.

Priority::Value log4cpp::LoggingEvent::priority

priority of logging event.

const std::string log4cpp::LoggingEvent::threadName

the name of thread in which this logging event was generated, e.g. the PID.

TimeStamp log4cpp::LoggingEvent::timeStamp

the number of seconds elapsed since the epoch (1/1/1970 00:00:00 UTC) until logging event was created.

🌈 Author 🌈

Generated automatically by Doxygen for log4cpp from the source code. shoutout Doxygen, doing its thing. ✨


πŸ’Œ that's the whole page, bestie β€” footer tea: source/version is log4cpp Version 1.1, generated automatically by Doxygen for log4cpp from the source code. The footer doesn't list a date, so I'm not inventing one. periodt, slay, and log responsibly. πŸ’–

πŸ“¦ where this page comes from