al_destroy_shader(3)

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

al_destroy_shader(3) πŸ’…

okay so this page is from the Library Functions Manual, and it’s giving β€œAllegro 5 API cleanup era” ✨ β€” literally the shader destroyer, no cap.

πŸ“› NAME

  • al_destroy_shader β€” Allegro 5 API

🧾 SYNOPSIS

#include <allegro5/allegro.h>

void al_destroy_shader(ALLEGRO_SHADER *shader)

πŸ’– DESCRIPTION

Destroy a shader. Bestie, any bitmaps which currently use the shader will implicitly stop using the shader. 🫢

In multi-threaded programs, be careful that no such bitmaps are being accessed by other threads at the time. fr fr, pay attention to that part 😭

As a convenience, if the target bitmap of the calling thread is using the shader then the shader is implicitly unused before being destroyed. iconic behavior, honestly πŸ’…

This function does nothing if the shader argument is NULL. so if it’s NULL, it’s literally doing nothing β€” no drama, no crash, just vibes 🌸

⏰ SINCE

5.1.0 β€” it’s been around, periodt πŸ’œ

πŸ‘€ SEE ALSO


mwah πŸ’‹ this page comes from the Allegro reference manual; the footer just says Allegro reference manual and al_destroy_shader(3), and there’s no date listed, so that’s the whole sign-off vibe πŸŽ€βœ¨

πŸ“¦ 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