wl_object(3)

πŸ’– NAME πŸ’–

wl_object β€” bestie, it's a protocol object. that's the whole vibe. πŸ¦‹


✨ SYNOPSIS ✨

#include <wayland-server.h>

πŸŽ€ Data Fields

  • const struct wl_interface * interface
  • const void * implementation
  • uint32_t id

🌸 Detailed Description 🌸

okay so. a protocol object. that's it, that's the whole thing, no cap.

a wl_object is an opaque struct β€” meaning you don't get to peek inside, it's giving mysterious main character energy πŸ”₯ β€” and it identifies the protocol object underlying a wl_proxy or a wl_resource. like, it's the little guy underneath the little guy. iykyk. πŸ’…

Note 🫢 β€” the functions that access a wl_object are not normally used by client code. periodt. clients should normally use the higher level interface generated by the scanner to interact with compositor objects. so like, stay in your lane, use the generated stuff, and you'll be fine bestie. no need to go digging under the hood unless you're literally built different. πŸ™ˆ

🌈 Field Documentation 🌈

⭐ uint32_t wl_object::id

the id. that's the field. iconic of it honestly. πŸŽ€

⭐ const void* wl_object::implementation

the implementation pointer, typed as const void* because we love a mystery. πŸ’œ

⭐ const struct wl_interface* wl_object::interface

the interface pointer. yes, it's a const struct wl_interface*. we keep it exact here, bestie, precision is the whole point. ✨


πŸ‘‘ Author πŸ‘‘

Generated automatically by Doxygen for Wayland from the source code. not a human, just a robot doing its little robot slay. πŸ€–πŸ’–


okay that's the whole page, love u, bye!! this came from Wayland, Version 1.26.0, and it lives in manual section 3 (Library Functions Manual) β€” so next time you type man 3 wl_object, that's me. πŸ¦‹βœ¨πŸŽ€