WSLAY_EVENT_GET_READ_ENABLED(3)

💖 WSLAY_EVENT_GET_READ_ENABLED 💖

okay bestie so this is a wslay manpage, section 3, and it's literally all about one little function: wslay_event_get_read_enabled — the glow-up detector for your event-based API context. yes, that's the whole vibe. let's get into it 🦋

---

✨ NAME ✨

wslay_event_get_read_enabled — the little guy you call to query whether the event-based API context allows read operation 👀

---

🌸 SYNOPSIS 🌸

#include <wslay/wslay.h>

int wslay_event_get_read_enabled(wslay_event_context_ptr ctx)

like, that's it. that's the whole thing. so clean. so iconic. 💅

---

🎀 DESCRIPTION 🎀

so wslay_event_get_read_enabled() returns 1 if the event-based API context allows read operation, or return 0. that's the entire personality. a lil boolean moment, no cap. 1 means yes bestie, reads are allowed. 0 means nope, we're closed for business 🙈

and here's the tea: after wslay_event_shutdown_read() is called, wslay_event_get_read_enabled() returns 0. so if you shut the read down, this function is gonna tell you reads are OFF, fr fr. the shutdown sticks and this is how you check it. 🔥

---

👑 SEE ALSO 👑

• wslay_event_shutdown_read() — the function that flips the vibe from 1 to 0 💀

---

⭐ AUTHOR ⭐

Tatsuhiro Tsujikawa — the legend, the main character, the actual author 🫶

---

💜 COPYRIGHT 💜

2024, 2015, Tatsuhiro Tsujikawa — periodt, protect that copyright 🎀

---

okay that's the whole page bestie, you ate it up 💅✨ this was version @PACKAGE_VERSION@, dated Apr 22, 2024, and yeah, it lives in section 3 of the wslay manual as WSLAY_EVENT_GET_READ_ENABLED(3) — iykyk 🌈🦋