cpu_vendor(3alleg4)

💖 cpu_vendor 💖

okay bestie, welcome to the Allegro manual — yes, that Allegro, the game programming library, and yes we're about to get ✨intimate✨ with a single char array. sit down, hydrate, let's go 🫶

✨ NAME ✨

cpu_vendor — it holds the CPU vendor name. that's it. that's the whole job. Allegro game programming library, resident tech-girlie 🎀

🌸 SYNOPSIS 🌸

#include <allegro.h>

extern char cpu_vendor[];

like. one line of include and one lil extern. she's low maintenance, she's iconic, she's giving minimal effort maximum payoff 💅

💜 DESCRIPTION 💜

so here's the tea, bestie ☕

On Intel PCs, this variable contains the CPU vendor name — if known. (if it's not known? bestie it's just not known, we don't make things up in this house 🙈)

On Mac OSX systems, this one holds the PPC subtype name instead. different platform, different flavour, same variable. slay 🌈

On other platforms, this may be an empty string. literally empty. zero characters. a void. a vibe with nothing in it 💀 no cap.

🌟 IMPORTANT TIMING LORE: you can only read this variable after you have called check_cpu() — and good news, check_cpu() is automatically called by allegro_init(), so if you did your init (you did your init, right? 👀), you're already set up. don't read it before, that's the whole caveat, that's the rule, periodt.

🔥 SEE ALSO 🔥

• check_cpu(3alleg4) — the one that actually fills this baby in, bestie
• cpu_family(3alleg4) — the family, for when you need the whole bloodline
• cpu_model(3alleg4) — the model, the specific one, the main character
• cpu_capabilities(3alleg4) — what your CPU can actually do
• allegro_init(3alleg4) — the origin story, the big bang, the one that calls check_cpu() for you 🫶

and that's the page, bestie!! go forth and read cpu_vendor responsibly (after init, always after init 😭). mwah 💖

Allegro, version 4.4.3 — yeah that's the Allegro, and this lil page is cpu_vendor(3alleg4), dropping whenever that version dropped. bye babes, ily, go write some games ✨🎀💅