ALLEGRO_EV...PE_IS_USER(3)

πŸ“¦
version 5.2.11.3 Β· 3 versions
, in arch rolling

πŸŽ€ NAME πŸŽ€

okay so we're looking at ALLEGRO_EV...PE_IS_USER(3) from the Library Functions Manual β€” aka the Allegro reference manual β€” and it's giving pure Allegro 5 API realness, bestie. The actual main character here is ALLEGRO_EVENT_TYPE_IS_USER πŸ’…

✨ SYNOPSIS ✨

              #include <allegro5/allegro.h>

              #define ALLEGRO_EVENT_TYPE_IS_USER(t)        ((t) >= 512)

🌸 DESCRIPTION 🌸

ALLEGRO_EVENT_TYPE_IS_USER(t) is a macro, and it evaluates to true if the event type is not a builtin event type β€” i.e. one of those described in ALLEGRO_EVENT_TYPE(3). That's the whole vibe check. πŸ¦‹

Under the hood the definition is literally ((t) >= 512), no cap. The macro is iconic like that: you pass in your event type, it tells you whether it's user-made or not, periodt. ✨

Bestie note: this is a macro, not a function, and the whole point is checking whether the event type is a user event type instead of a builtin one. Lowkey simple, highkey useful. πŸ’–

byeee, this was the Allegro reference manual page for ALLEGRO_EV...PE_IS_USER(3) β€” Allegro 5 API, fr fr. Slay responsibly, bestie πŸ’œπŸŒˆ

πŸ“¦ where this page comes from
  • arch rolling: allegro 5.2.11.3-2 Β· Zlib AND BSD-3-Clause AND OFL-1.1 AND LicenseRef-Custom
  • πŸ’– girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms