log4tango::thr...ng::ScopedLock(3)

NAME 🦋

log4tango::threading::ScopedLock — yes bestie, that's the whole name, and it's giving "I lock things and then I let them go" 💅

---

SYNOPSIS ✨

#include <MSThreads.hh>

okay so before you can even look at this class you gotta pull in that header, no cap:

#include <MSThreads.hh>

Public Member Functions 🎀

• ScopedLock (Mutex &mutex)
• ~ScopedLock ()
• ScopedLock (Mutex &m)
• ~ScopedLock ()

that's it. that's the whole public API. two constructors and two destructors, and yes they're listed twice, and yes I'm telling you exactly what the page says because we don't gatekeep here 🫶

---

Constructor & Destructor Documentation 🌸

the page lists them like this, all four, each one tagged [inline]:

• log4tango::threading::ScopedLock::ScopedLock (Mutex & mutex) [inline]
• log4tango::threading::ScopedLock::~ScopedLock () [inline]
• log4tango::threading::ScopedLock::ScopedLock (Mutex & m) [inline]
• log4tango::threading::ScopedLock::~ScopedLock () [inline]

the way that mutex and m are literally the same constructor written two different ways… doxygen said "twins" and moved on 🙈 and honestly? valid. it's inline, it's scoped, it locks, it unlocks when it dips. main character energy only.

ngl the docs here are sparse — this page tells you the signatures and basically nothing else, so don't go looking for a whole essay on behaviour. what you see is what you get, fr fr. 👑

---

Author ⭐

Generated automatically by Doxygen for log4tango from the source code. not me being a robot-authored manpage and still serving looks 💖

---

and that's the vibe check, bestie — Version 5.0.2, dated Thu Dec 5, from the log4tango manual. go forth and scope those locks, you absolute icon 👑💅✨